Lars wrote: > I installed Bind9 on a DomU running etch > (2.6.18-4-xen-vserver-amd64), and bind couldn't start with default > configuration. > # /etc/init.d/bind9 restart > Stopping domain name service...: bindrndc: connect failed: > 127.0.0.1#953: connection refused > failed! > Starting domain name service...: bind failed!
This is an indication that a named is running but the 'rndc' command failed to communicate with it. This usually happens when a named was started outside of the init scripts. Use 'ps -ef | grep named' to find all occurrences of running named processes, kill them all, then restart. (Or use 'pkill named' or 'killall named' if you happen to have those commands installed.) > I tried chmod 777 /etc/bind and named.conf, but it made no > difference. Please restore the original permissions. This would be: sudo chown root:bind /etc/bind /etc/bind/named.conf sudo chmod 02755 /etc/bind sudo chmod 0644 /etc/bind/named.conf > I then tried to rename named.conf, but the same error in > syslog appears. Right. The named needs a configuration file. > I've installed Bind9 on another DomU and it was the same error, so > it's something Xens DomU have in common. > I've installed Bind9 on Dom0, just to see if it was something with > the 64bit part, but here it started perfect with the default conf. > So it's only with the DomU's You will probably have to debug the problem then. I am assuming that the virtual machine has a unique ip address? Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
