Class C in-addr.arpa delegation, am I doing this correctly?

Ray Van Dolson rayvd at digitalpath.net
Sat Nov 19 01:10:24 UTC 2005


We have a /19 reallocated to us from Sprint.

Of that, I would like to delegate reverse DNS authority for a /24 to
another ISP's nameserver's.

Using the REASSIGN forms on ARIN do not work--complains about not being
a /16.

Apparently our ISP (Sprint) is therefore delegating 8 /24's to us
individually since we are only receiving a /19 from them.  So to
delegate a /24 from that to our customer ISP I am doing the following:

$TTL 86400      ; max TTL

$ORIGIN 254.62.192.in-addr.arpa.
@       IN      SOA     ns1.digitalpath.net.
hostmaster.digitalpath.net. (
                                2005111836      ;       Serial
                                28800           ;       Refresh
                                7200            ;       Retry
                                604800          ;       Expire
                                3600 )          ;       TTL Minimum
@               IN      NS      ns1.digitalpath.net.
@               IN      NS      ns2.digitalpath.net.

$ORIGIN .
$GENERATE 1-255 $.254.62.192.in-addr.arpa.      NS      NS01.ISP.COM.
$GENERATE 1-255 $.254.62.192.in-addr.arpa.      NS      NS02.ISP.COM.
$GENERATE 1-255 $.254.62.192.in-addr.arpa.      NS      NS03.ISP.COM.
$GENERATE 1-255 $.254.62.192.in-addr.arpa.      NS      NS04.ISP.COM.

(IP's changed to protect the guilty)

This seems to work with a couple oddities:

Automatic AXFR's of the zone with the GENERATE macro run does not
appear to move over to ns2.digitalpath.net (my secondary nameserver).
I am doing a dig @ns1 254.62.19.in-addr.arpa axfr > zonefile on
ns2.digitalpath.net to bring the zonefile over.  The GENERATE macro is
expanded correctly here.

Reverse DNS resolution from out on the internet of one of these IP's
still doesn't appear to work.  No valid IP is returned.  Maybe this is
a propagation issue, so I will give it a day.

Using dnstracer -s . -c -C -o -4 1.254.62.192.in-addr.arpa shows the
NS01.ISP.COM, etc nameservers under ours, so at least that appears to
be working correctly.

Thanks for pointing out any problems.



More information about the bind-users mailing list