zone troubles after upgrade

[Barry Margolin]

In article <bm45h8$onn$1 at sf1.isc.org>, Lost Soul <nobody at nowhere.com> wrote:
>I just recently upgraded to BIND 9.2.2-P3 and now when I try to lookup
>anything on a zone I've got set up using the RFC 2317 specs fails.
>Attempting to dig from a source that uses the local view returns SERVFAIL.
>If I try to lookup something remotely with debugging set to 3,4,5, or 10, I
>get the following in the logs:
....
>The entry for the zone in named.conf and the zone file itself look as
>follows:
>
>        zone "176/29.201.20.68.in-addr.arpa" {
>                type master;
>                file "master/external/176.201.20.68.in-addr.arpa";
>        };

The name of the subdomain that Ameritech has delegated to you is
"176.201.20.68.in-addr.arpa", there is no "/29" in the zone name.

>----------
>TTL 1D

That should be "$TTL 1D".

>$ORIGIN 176/29.201.20.68.in-addr.arpa.

This should also not have "/29".  Why do you bother with a $ORIGIN
statement at all, since the default is the zone name from the named.conf
file?  Having it here is just an opportunity for more errors (if you change
the zone statement but forget to change it here).

>@       IN      SOA     cataloging.lab-ratz.net. admin.lab-ratz.net. (
>                        2003100901      ; serial
>                        1200            ; refresh
>                        7200            ; retry
>                        1209600         ; expiry
>                        86400 )         ; minimum
>
>        IN      NS      cataloging.lab-ratz.net.
>        IN      NS      ns1.ameritech.net.
>        IN      NS      ns2.ameritech.net.
>
>177     IN      PTR     delivering.lab-ratz.net.
>177     IN      PTR     cataloging.lab-ratz.net.
>178     IN      PTR     researching.lab-ratz.net.
>182     IN      PTR     injecting.lab-ratz.net.
>
>named-checkzone returns the following:

I'm not sure what caused all the "out-of-zone data" errors.  That's what
would happen if you changed the zone name in named.conf but forgot to
change the $ORIGIN statement.

># named-checkzone -q 176/29.201.20.in-addr.arpa
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa
>[root at cataloging etc]# named-checkzone 176/29.201.20.in-addr.arpa
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa
>dns_master_load:
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa:3: ignoring
>out-of-zone data (176/29.201.20.68.in-addr.arpa)
>dns_master_load:
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa:14: ignoring
>out-of-zone data (177.176/29.201.20.68.in-addr.arpa)
>dns_master_load:
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa:15: ignoring
>out-of-zone data (177.176/29.201.20.68.in-addr.arpa)
>dns_master_load:
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa:16: ignoring
>out-of-zone data (178.176/29.201.20.68.in-addr.arpa)
>dns_master_load:
>/var/named/var/named/master/external/176.201.20.68.in-addr.arpa:17: ignoring
>out-of-zone data (182.176/29.201.20.68.in-addr.arpa)
>zone 176/29.201.20.in-addr.arpa/IN: could not find NS and/or SOA records
>zone 176/29.201.20.in-addr.arpa/IN: has 0 SOA records
>zone 176/29.201.20.in-addr.arpa/IN: has no NS records
>
>Any ideas?
>
>
>


-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.