Bind behaves weirdly
jc pinoteau
jc.pinoteau at laposte.net
Mon Dec 27 22:06:25 UTC 2004
I am using bind 9.2.3 for caching only on several gateways with different
ISPs. On one of them I get weird results. It won't resolve google.com (for
instance) for a few hours then it would do it again (without any action from
my part). It will give the same result as if I was digging on a non existing
domain.
It is not a problem with the ISP as digging on the ISP's DNS returns a good
result.
If I restart bind it works again.
How can I analyse what is happening?
Here is my configuration file:
// generated by named-bootconf.pl
// secret must be the same as in /etc/rndc.conf
key "key" {
algorithm hmac-md5;
secret
"c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};
controls {
inet 127.0.0.1 allow { any; } keys { "key"; };
};
options {
pid-file "/var/run/named/named.pid";
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;
forward first;
forwarders {
195.68.0.1;
195.68.0.2;
};
};
//
// a caching only nameserver config
//
zone "." {
type hint;
file "named.ca";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
};
// workaround stupid stuff... (OE: Wed 17 Sep 2003)
zone "ac" { type delegation-only; };
zone "cc" { type delegation-only; };
zone "com" { type delegation-only; };
zone "cx" { type delegation-only; };
zone "museum" { type delegation-only; };
zone "net" { type delegation-only; };
zone "nu" { type delegation-only; };
zone "ph" { type delegation-only; };
zone "sh" { type delegation-only; };
zone "tm" { type delegation-only; };
zone "ws" { type delegation-only; };
More information about the bind-users
mailing list