Revers Zone

[Matt Larson]

At 12:16 AM 8/18/99 +0000, eastk wrote:
>Thanks to everyone for the info.  I did not have another domain with cnames
>in them.  I am reluctant to use this method as it will be quite a
>administratively nightmare on a class A address.  Do most people with class
>a reverse zones maintain one file like 10.in-addr.arpa?

No.  Most people delegate.  That's what we did at HP with network 15.0.0.0, 
for example.

I was hoping QIP 5 would get in-addr.arpa zones right...

Using the RFC 2317/CNAME method for subnets larger than /24s is possible, 
but so is driving your car everywhere only in first gear--you don't want to 
do it.  As Barry said in a prior post, you should be delegating.  For 
example, assuming network 10.0.0.0 subnetted into /22s, you'd want NS 
records in your 10.in-addr.arpa zone data file for each subnet.  In your 
case, four /24-sized in-addr.arpa zones to equal one /22 subnet.  So for 
the first subnet (10.0.4/22), you'd have:

4.0.10.in-addr.arpa.  in  ns  ns1.foo.com.
4.0.10.in-addr.arpa.  in  ns  ns2.foo.com.
5.0.10.in-addr.arpa.  in  ns  ns1.foo.com.
5.0.10.in-addr.arpa.  in  ns  ns2.foo.com.
6.0.10.in-addr.arpa.  in  ns  ns1.foo.com.
6.0.10.in-addr.arpa.  in  ns  ns2.foo.com.
7.0.10.in-addr.arpa.  in  ns  ns1.foo.com.
7.0.10.in-addr.arpa.  in  ns  ns2.foo.com.

(Assuming two name servers per in-addr.arpa zone.  Obviously you could have 
more.)  Repeat these NS records for every subnet.

If QIP can't let you delegate like this within the in-addr.arpa name space, 
it's broken.

Matt

--
Matt Larson <matt at acmebw.com>
Acme Byte & Wire / http://www.acmebw.com