I've been running BIND for a while now, and it seems to work just fine for me, but some people are still having issues with the DNS resolving to the new server. I know what you're thinking -- that the nameserver entries just haven't been updated for them yet, but I made the DNS changes to point to my own server over a month ago. I've also gotten some error messages from LogWatch that just says "DNS: local configuration error: 6 Time(s)", so I know something must be wrong with my setup.
Here's my zone file:
;Begin of file /var/named/kitsapbands.zone
$TTL 43200
@ IN SOA ns1.kitsapbands.com. postmaster.kitsapbands.com. (
2000032701 ; Serial
300 ; Refresh - 5 Minutes
60 ; Retry - 1 minute
1209600 ; Expire - 2 Weeks
43200) ; Minimum - 12 Hours
IN NS ns1.kitsapbands.com.
IN MX 10 mail.kitsapbands.com.
IN A 64.113.1.119
www IN A 64.113.1.119
mail IN A 64.113.1.119
ns IN A 64.113.1.119
ftp IN CNAME
www.kitsapbands.com.
;EOF
and here's my named.conf:
// generated by named-bootconf.pl
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
//controls {
// inet 127.0.0.1 allow { localhost; } keys { rndckey; };
//};
zone "." {
type hint;
file "named.ca";
};
zone "kitsapbands.com" {
type master;
file "kitsapbands.zone";
};
zone "localhost" {
type master;
file "localhost.zone";
// allow-update { none; };
};
zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
// allow-update { none; };
};
Any ideas here?
