bind 9.7.2-4.P3 in f14 not working with previous reverse lookup zone file
dave perry
skidavem at mindspring.com
Tue Dec 14 05:04:15 UTC 2010
Hi,
I decided to update a home dns server to fc14 (was running fc9). I
can't get bind to accept a zone file that worked with fc12 bind.
named-checkconf returns OK so my old named.conf seem not the problem.
The zone file contents being rejected follow:
$TTL 86400
@ IN SOA ns1.colo-perrys.com.
hostmaster.colo-perrys.com. (
2010121301 ; Serial
28800 ;
Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ;
Minimum
IN NS ns1.colo-perrys.com.
100 IN PTR colo-perrys.com.
2 IN PTR dadsoffice.colo-perrys.com.
9 IN PTR mobile1.colo-perrys.com.
10 IN PTR unclecarl.colo-perrys.com.
4 IN PTR Dave-PC.colo-perrys.com.
20 IN PTR Linksys-WAP54G.colo-perrys.com.
;EOF
The error message returned by
named-checkzone colo-perrys.com /var/named/chroot/var/named/perrylan.db
is
zone colo-perrys.com/IN: NS 'ns1.colo-perrys.com' has no address records
(A or AAAA)
If I replace 'colo-perrys.com' with '1.168.192.in-addr.arpa', the zone
name from named.conf, then named-checkzone returns OK. But service
named start still fails.
My /etc/named.conf contains
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
};
acl "mylan" {
127/8; 192.168.1.0/24;
};
#controls {
# inet 127.0.0.1 allow { localhost; } keys { rndckey; };
#};
view "inside" {
match-clients { "mylan"; };
recursion yes;
zone "." IN {
type hint;
file "named.ca";
};
zone "1.168.192.in-addr.arpa" IN {
type master;
file "perrylan.db";
};
zone "colo-perrys.com" {
type master;
file "db.colo-perrys.com.inside";
allow-transfer { 192.168.1.101; };
};
};
Can anyone point me to what I'm missing?
Thanks,
Dave P.
More information about the users
mailing list