Zone Authority Subnets

Brenden Eng brendeneng at gmail.com
Thu Oct 20 05:15:08 UTC 2005


I have searched a while for this, but here is what I have come to conclude.
in-addr.arpa does not understand classless boundaries.

If the name servers for 1.2.160.0/20 <http://1.2.160.0/20> are set to my
own, then I have authority over this zone.

I made a entry in bind9 config:

zone "2.1.in-addr.arpa" {
        type master;
        file "/etc/bind/db.2.1.0.0";
};


This way, the server will answer all of those requests.

$TTL 900
@        IN      SOA    ns1.mydomain.com <http://ns1.mydomain.com>.   
   admin.mydomain.com <http://admin.mydomain.com>. (
2005102000 ; Serial Number
900 ; Refresh after 3 hours
900 ; Retry after 1 hour
604800 ; Expire after 1 week
900 ) ; Minimum TTL of 1 day

        IN      NS ns1.mydomain.com <http://ns1.mydomain.com>.
        IN      NS ns2.mydomain.com <http://ns2.mydomain.com>.

1.160.2.1.in-addr.arpa.     IN      PTR     mail.mydomain.com
<http://mail.mydomain.com>.


Yes, this works great and all, until further inspection.

`host 1.2.160.1` shows mail.mydomain.com <http://mail.mydomain.com>

However:

dig 160.2.1.in-addr.arpa

Fails! Why? I think its because there is no authority for that 'class b'
(/24) zone.

Besides making separate zone files for each of my 1.2.[160-175] 'class b'
zones, what can I do instead?

host -t ns 160.2.1.in-addr.arpa

Fails as well.


How can I resolve this?
Thank you



More information about the bind-users mailing list