172.16/12 Reverse Maps Don't work.

[doon k]

Not sure what that PTR record in your zone is supposed to be, but
since the zone is 16.172.in-addr.arpa, try adding the following
record:

1.1   IN   PTR   test.record.

Now do a query for the record 172.16.1.1 and it should resolve to test.reco=
rd. =20



On 6/16/05, Chris <chris at pop.ucsd.edu> wrote:
>=20
> "Martin McCormick" <martin at dc.cis.okstate.edu> wrote in message
> news:d8sopp$9a4$1 at sf1.isc.org...
> > We have bind9 correctly serving several private-network zones
> > but I can't for the life of me, get the reverse map for
> > 172.16.IN-ADDR.ARPA. to work at all.
> >
> > The start of the zone looks like:
> >
> > ;
> > ; 16.172.in-addr.arpa
> > ;
> >
> > $TTL 43200
> > @       IN     SOA  ns.xyz. martin.dc.cis.okstate.edu.  (
> >                                1; Serial
> >                                    14400; Refresh
> >                                    900; Retry
> >                                  1209600; Expire
> >                                   30 ) ;Minimum
> >  IN NS ns.xyz.
> >  IN NS ns2.xyz.
> > 1.16.172.IN-ADDR.ARPA. 43200 IN PTR ns.xyz.
> >
> > All reverse queries to 172.16.1.1 take what I frustratedly
> > like to call the thousand-mile route in that, instead of going across
> > the room where they physically are, they get a bit lost out there in
> > the Internet.
> >
> > dig @172.16.1.1 172.22.12.4 -x (an address registered in the network)
> >
> >
> > ; <<>> DiG 9.2.3 <<>> @172.16.1.1 -x 172.22.12.4
> > ;; global options:  printcmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26347
> > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> >
> > ;; QUESTION SECTION:
> > ;4.12.22.172.in-addr.arpa. IN PTR
> >
> > ;; AUTHORITY SECTION:
> > 22.172.in-addr.arpa. 9594 IN SOA prisoner.iana.org.
> > hostmaster.root-servers.org. 1 604800 60 604800 604800
> >
> > ;; Query time: 1 msec
> > ;; SERVER: 172.16.1.1#53(172.16.1.1)
> > ;; WHEN: Thu Jun 16 15:18:23 2005
> > ;; MSG SIZE  rcvd: 119
> >
> >
> > The name server log says that the zone successfully loaded but
> > lookups can't find any reverse information.
> >
> > We did have reverse lookups in that network working when we
> > had a Class C-sized subnet active at 172.16.1/24.  It only broke when
> > I thought I redefined the IN-ADDR.ARPA. zone to encompass the entire
> > /12 network from 172.16.0.1 through 172.35.255.254.
> >
> > Any ideas as to why this isn't working?
> >
> > Thank you.
>=20
> Am I missing something here? You have created a zone on your server for
> 1.16.172.in-addr.arpa but then you are doing a reverse lookup on
> 172.22.12.4. Have you also created a reverse zone for 12.22.172.in-addr.a=
rpa
> as well or not?
>=20
> The address that you are digging for, 172.22.12.4 will not be in a
> 16.172.in-addr.arpa zone.
>=20
> Chris.
>=20
>=20
>=20
>