zone troubles after upgrade
Lost Soul
nobody at nowhere.com
Thu Oct 9 10:43:41 UTC 2003
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:
Oct 09 02:18:55.856 client 69.2.200.182#4766: UDP request
Oct 09 02:18:55.857 client 69.2.200.182#4766: using view 'external-in'
Oct 09 02:18:55.858 client 69.2.200.182#4766: request is not signed
Oct 09 02:18:55.858 client 69.2.200.182#4766: query
Oct 09 02:18:55.858 client 69.2.200.182#4766: query:
178.176.201.20.68.in-addr.arpa IN PTR
Oct 09 02:18:55.858 client 69.2.200.182#4766: error
Oct 09 02:18:55.858 client 69.2.200.182#4766: send
Oct 09 02:18:55.859 client 69.2.200.182#4766: sendto
Oct 09 02:18:55.859 client 69.2.200.182#4766: senddone
Oct 09 02:18:55.859 client 69.2.200.182#4766: next
Oct 09 02:18:55.859 client 69.2.200.182#4766: endrequest
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";
};
----------
TTL 1D
$ORIGIN 176/29.201.20.68.in-addr.arpa.
@ 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:
# 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?
More information about the bind-users
mailing list