Subnetted Reverse DNS - Going crazy

[aad]

On Nov 6, 2007 5:49 PM, Andrew Hydle <ahydle at gmail.com> wrote:
> Unfortunately I cant get verizon to do anything yet because I cannot resolve
> the zone locally. There software does a DNS verification to make sure that
> the zone is configured before they delegate it. But the zone is not working
> at all on our servers so they cannot delegate it.

Take a look at the last example in RFC 2317 ("alternative approach")
and then simply rename your zone in named.conf to
"208.130.212.65.in-addr.arpa" to match the naming convention
UUNET/MCI/VerizonBusiness is looking for (at least based on how they
"used to" do their subnetted reverse a few years ago).

And again, talk to Verizon and verify the expected naming convention,
how they're delegating to you and how they're expecting your server to
respond.

--ali


> On 11/6/07, Mark Andrews <Mark_Andrews at isc.org> wrote:
> >
> >
> > > I have been assigned a /28 ip range and am having some issues setting up
> > > reverse dns.
> >
> >        Talk to Verizon.  You and them need to decide how this
> >        delegation will be performed.  See RFC 2317 for details.
> >        They will have done this before and will have a prefered
> >        convention (208-223.130.212.65.in-addr.arpa vs
> >        208/28.130.212.65.in-addr.arpa vs ....).
> >
> >        You should also make yourself a slave to 130.212.65.in-addr.arpa.
> >        That way you will have the CNAMEs locally when your link goes
> >        down.  This will allow you nameserver to map between the well
> >        known names and the names you are actually using to hold the
> >        PTR records.
> >
> >                zone "130.212.65.in-addr.arpa" {
> >                        type slave;
> >                        file "130.212.65.in-addr.arpa";
> >                        notify no;
> >                        masters { 198.6.100.21; };
> >                };
> >
> >        Mark
> >
> > > So far I have tried setting up my named.conf two ways:
> > > named.conf:
> > > zone "208-223.130.212.65.in-addr.arpa" IN {
> > >         type master;
> > >         file "65.212.130.rev";
> > >         allow-update { none; };
> > >         allow-query { any; };
> > > };
> > >
> > > or
> > >
> > > zone "208/28.130.212.65.in-addr.arpa" IN {
> > >         type master;
> > >         file "65.212.130.rev";
> > >         allow-update { none; };
> > >         allow-query { any; };
> > > };
> > >
> > > and I have my db file setup like so:
> > >
> > >
> > > $TTL    43200
> > > @       IN      SOA     dns2.external.com. mail.external.com.  (
> > >                                       2007110601 ; Serial
> > >                                       1H    ; Refresh
> > >                                       30M   ; Retry
> > >                                       2D    ; Expire
> > >                                       12H )  ; Minimum
> > >
> > >         IN      NS      dns2.external.com.
> > >         IN      NS      dns1.external.com.
> > >
> > > 210     IN      PTR     hosta.com.
> > > 220     IN      PTR     hostb.com.
> > >
> > > If I do an nslookup I get:
> > >
> > > ** server can't find 220.130.212.65.in-addr.arpa: NXDOMAIN
> > >
> > > and Dig gives me the same information showing that the ip is hosted with
> > my
> > > ISP. I am trying to get this working so that my ISP can delegate the
> > domain.
> > >
> > > If I set the zone to a class c I can resolve properly so I know it isnt
> > a
> > > formatting issue in by db file but I cannot figure out what I am doing
> > > wrong. Can someone please help?
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org
> >
>
>
>
>