in-addr.arpa delegation failure
Lars Hecking
lhecking at users.sourceforge.net
Wed Jan 21 18:10:34 UTC 2009
Stephane Bortzmeyer writes:
[...]
> IMHO, you need to go back to the drawing board and, before writing
> named.conf and zone files, deciding on a general architecture.
>
> Who will be the master for 30.172.in-addr.arpa?
> Who will be authoritative for 30.172.in-addr.arpa?
> Who will be the master for 10.30.172.in-addr.arpa?
> Who will be authoritative for 10.30.172.in-addr.arpa?
I've solved it, I think. The top level ns is authority and master
for 30.172.in-addr.arpa, and the subnets are delegated to the subdomain
name servers. Nice application of $GENERATE :)
I prever not to set up the top level ns as a slave.
More information about the bind-users
mailing list