Ignoring out-of-zone data

[Mark Andrews]

> Hi,
> 
> Running Bind 9.3.0

	Upgrade.

> I have a Class C (207.191.185) and several domain names each with an IP 
> address from that Class C. jellico.com is my primary domain name. Before 
> upgrading to Bind 9, I had the other domain names listed in jellico.com.db 
> like so:
> 
> multi-230       IN      A       207.191.185.230
> tspma.com.      IN      A       207.191.185.231
> copperhill.com. IN      A       207.191.185.232
> multi-233       IN      A       207.191.185.233
> www.jellico.net.        IN      A       207.191.185.234
> jellicoalumni.com.      IN      A       207.191.185.235
> stair-way-to-heaven.com.        IN      A       207.191.185.236

	Well those other records shouldn't have been there and were
	most probably being silently ignored.
 
> They are also listed in 185.191.207.in-addr.arpa  plus each has it's own 
> zone file: tspma.com.db, etc.

	Which is the correct way to do it.
 
> After upgrading to Bind 9, Bind complains about ignoring out-of-zone data in 
> jellico.com.db
> 
> I took the entries for the other domain names out of jellico.com.db and now 
> when I reload the name server it reloads without complaint.

	Good.
 
> The domain that I'm most concerned with right now is jellico.net  It's IP 
> address is 207.191.185.4  I took it out of jellico.com.db, but it is still 
> listed in  185.191.207.in-addr.arpa  like so:
> 
> 4       IN      PTR     jellico.net.
> 
> and it has it's own zone file: jellico.net.db which looks like this:
> 
> ; Authoritative data for jellico.net
>           ; zone jellico.net
> $TTL  3600
> jellico.net.       IN      SOA  ns.jellico.net. root.jellico.net.  (
>                                 200611091       ; Serial
>                                 3600            ; Refresh one hour
>                                 900             ; Retry 15 minutes
>                                 604800          ; Expire one week
>                                 3600 )          ; Minimum TTL one hour
> ;
> ;  Nameservers
> ;
>                 IN      NS      ns.jellico.net.
>                 IN      NS      bluegrass.tcnet.net.
> 
>                 IN      MX 10   mail.jellico.com.
>                 IN      MX 20   bluegrass.tcnet.net.
> 
> jellico.net.    IN      A       207.191.185.4
> ns              IN      A       207.191.185.4
> www             IN      A       207.191.185.234
> 
> ns.jellico.net.         IN      A       207.191.185.4
> 
> 
> If I go to dnsstuff.com, I can resolve jellico.net to it's IP address, but I 
> cannot resolve the IP address back to jellico.net (reverse DNS isn't working 
> for this domain). So AOL will not accept mail from this domain. What have I 
> got wrong here?

	185.191.207.in-addr.arpa is delegated to these servers.

185.191.207.in-addr.arpa. 3600  IN      NS      ns1.butler.net.
185.191.207.in-addr.arpa. 3600  IN      NS      ns2.butler.net.

	Given the addresses above you most probably want to get the
	zone delegated to your servers instead.  It looks like you
	have the whole /24 (207.191.185.0 ... 207.191.185.255).

	If you don't have the whole /24 then you need to contact
	whomever is administrating ns1.butler.net and ns2.butler.net
	and get them to delegate the reverse space for the addresses
	you are using.  This can be as individual zones for each
	address or by using the technic described in RFC 2317.

	Mark

> Thanks,
> 
> Lisa Casey
> 
> 
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org