IN-ADDR.ARPA Zone Delegations

Merton Campbell Crockett m.c.crockett at adelphia.net
Wed Jan 10 14:46:09 UTC 2007


On 10 Jan 2007, at 06:34:46, Merton Campbell Crockett wrote:

> What is a proper method of delegating IN-ADDR.ARPA zones?
>
> To delegate subdomains of a domain, I have created zone files like  
> the following.
>
> 	1.160.10.10.IN-ADDR.ARPA	PTR record for NS.SUB.DOMAIN.COM
> 	NS.SUB.DOMAIN.COM		A record for NS.SUB.DOMAIN.COM
>
> This allowed me to override the contents of the 10.10.IN-ADDR.ARPA  
> domain and define forward zones whilst transitioning parts of our  
> organisation from Microsoft to ISC DNS.
>
> The master name server's configuration file defined 10.10.IN- 
> ADDR.ARPA as a slave zone, the 1.160.10.10.IN-ADDR.ARPA as a master  
> zone, and 160.10.10.IN-ADDR and 161.10.10.IN-ADDR.ARPA as forward  
> zones.  The result of this configuration was that the master name  
> server would ignore the data obtained from the Microsoft DNS server  
> for the IN-ADDR.ARPA subdomains delegated to NS.SUB.DOMAIN.COM.
>
> The transition is nearing completion and I want to make the master  
> name server the primary name server for 10.10.IN-ADDR.ARPA.   
> Unfortunately when I do this, the master name server stops  
> forwarding requests to NS.SUB.DOMAIN.COM and returns NXDOMAIN.  Not  
> exactly what I had intended. :)
>
> I'm sure its a trivial oversight on my part; however, I would  
> appreciate any pointers that might help me resolve this problem.

I forgot to note that I used a $ORIGIN statements in the 10.10.IN- 
ADDR.ARPA zone file instead of the following notation.

	160		IN	NS	NS.SUB.DOMAIN.COM.
	161		IN	NS	NS.SUB.DOMAIN.COM.


Merton Campbell Crockett
m.c.crockett at adelphia.net





More information about the bind-users mailing list