Starting domain name service bind failed
Hi
I used to use a caching only name server under Debian. When I start the same setting under grml, I get:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. failed! Starting domain name service...: bind failed!
What could be wrong?
Or, how to setup a caching only name server under grml?
Thanks
* T mlist4suntong@yahoo.com [20061031 22:15]:
I used to use a caching only name server under Debian. When I start the same setting under grml, I get:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. failed! Starting domain name service...: bind failed!
What could be wrong?
Take a look at the syslog.
regards, -mika-
On Tue, 31 Oct 2006 22:19:18 +0100, Michael Prokop wrote:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. failed! Starting domain name service...: bind failed!
What could be wrong?
Take a look at the syslog.
Oct 31 18:34:56 cxmr named[2554]: invalid command from 127.0.0.1#42763: bad auth
nothing else. Hmm... let's see:
There is still an old bind running:
bind 2554 1 0 Oct28 ? 00:00:00 /usr/sbin/named -u bind
Having killed it by 'kill 2554', I am able to start bind again, but with a little glitch:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connect failed: connection refused failed! Starting domain name service...: bind.
bind 3146 1 0 18:38 ? 00:00:00 /usr/sbin/named -u bind
The syslog seems to be normal though:
Oct 31 18:38:30 cxmr named[3146]: starting BIND 9.3.2-P1 -u bind Oct 31 18:38:30 cxmr named[3146]: found 1 CPU, using 1 worker thread Oct 31 18:38:30 cxmr named[3146]: loading configuration from '/etc/bind/named.conf' Oct 31 18:38:30 cxmr modprobe: WARNING: Not loading blacklisted module ipv6 Oct 31 18:38:30 cxmr named[3146]: no IPv6 interfaces found Oct 31 18:38:30 cxmr named[3146]: listening on IPv4 interface lo, 127.0.0.1#53 Oct 31 18:38:30 cxmr named[3146]: listening on IPv4 interface eth0, 192.168.2.100#53 Oct 31 18:38:30 cxmr named[3146]: command channel listening on 127.0.0.1#953 Oct 31 18:38:30 cxmr named[3146]: zone 0.in-addr.arpa/IN: loaded serial 1 Oct 31 18:38:30 cxmr named[3146]: zone 127.in-addr.arpa/IN: loaded serial 1 Oct 31 18:38:30 cxmr named[3146]: zone 255.in-addr.arpa/IN: loaded serial 1 Oct 31 18:38:30 cxmr named[3146]: zone localhost/IN: loaded serial 1 Oct 31 18:38:30 cxmr named[3146]: running
If I restart it again, I get back the same error:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. failed! Starting domain name service...: bind failed!
The syslog has the same message:
Oct 31 18:39:41 cxmr named[3146]: invalid command from 127.0.0.1#40741: bad auth
Ok, it is not that bad -- my named can be started, but not restarted.
Any explanation?
thanks
* T wrote [01.11.06 00:48]: Hi,
If I restart it again, I get back the same error:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. failed! Starting domain name service...: bind failed!
Ok, this meens, the key which rndc uses to stop the server is wrong.
Any explanation?
To start the server, there is no key needed. If you stop it, a key is needed. So the rndc key is wrong. I have also a solution, do an ,---- | mv /etc/bind/rndc.conf /etc/bind/rndc.conf.org `----
Btw. this is _not_ a bug in the debian package. The problem is imho, that grml ships that file.
thanks
HTH Uli
On Wed, 01 Nov 2006 01:43:48 +0100, Ulrich Dangel wrote:
If I restart it again, I get back the same error:
% /etc/init.d/bind9 restart Stopping domain name service...: bindrndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. failed! Starting domain name service...: bind failed!
Ok, this meens, the key which rndc uses to stop the server is wrong.... I have also a solution, ...
OMG, unbelievable knowledgeable people lurking here. :-)
* Ulrich Dangel grml@spamt.net [20061101 02:15]:
- T wrote [01.11.06 00:48]:
[problems with bind9]
I have also a solution, do an ,---- | mv /etc/bind/rndc.conf /etc/bind/rndc.conf.org `----
Btw. this is _not_ a bug in the debian package. The problem is imho, that grml ships that file.
Sorry, this wasn't my intention. Fixed for the upcoming release. Thanks, Ulrich!
regards, -mika-
participants (3)
-
Michael Prokop -
T -
Ulrich Dangel