Reverse nameserver entries in CIDR network
Mark_Andrews at isc.org
Wed Feb 22 08:16:10 UTC 2006
> I am trying to get my head around reverse nameserver entries :-)
> We have a network 82.130.64/18. This is implemented, as needs must, as
> 64 zone files, one for each /24 subzone (i.e., 64.130.82.in-addr.arpa
> through 127.130.82.in-addr.arpa).
> At present, I'm putting nameserver information in there which is
> identical for each subzone:
> @ IN NS dns1.ethz.ch.
> So regardless of which subzone is queried, nameserver information shows
> My question is, is this sensible, standard, expected...?
> I'm thinking perhaps all I really need is nameserver information in the
> first subzone, so someone that looks up the nameservers for 18.104.22.168
> gets the right info. The other addresses (say 22.214.171.124) aren't
> really special within the CIDR network, but they do look that way to the
> untutored eye (i.e., they look like /24 network addresses).
> What do others do with nameserver info for classless reverse networks?
You do exactly that for /9 - /15 and /17 - /23. For /25 - /32
you can use any of the methods in RFC 2317.
> Regards, K.
> Karl Auer (kauer at biplane.com.au) +61-2-64957160 (w/h)
> http://www.biplane.com.au/~kauer/ +61-428-957160 (mob)
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users