Hi 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!
Syslog: Jul 9 00:55:58 test named[1261]: starting BIND 9.3.4 -u bind Jul 9 00:55:58 test named[1261]: found 1 CPU, using 1 worker thread Jul 9 00:55:58 test named[1261]: loading configuration from '/etc/bind/named.conf' Jul 9 00:55:58 test named[1261]: none:0: open: /etc/bind/named.conf: permission denied Jul 9 00:55:58 test named[1261]: loading configuration: permission denied Jul 9 00:55:58 test named[1261]: exiting (due to fatal error) I tried chmod 777 /etc/bind and named.conf, but it made no difference. I then tried to rename named.conf, but the same error in syslog appears. 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 In README.Debian for bind9 a similar log error, also something with "none:0: open:", is mention. Although it was regarding the testing kernels 2.5. so I tried to recompile Bind9 with --disable-linux-caps. But i got an error when i started the installed package, something with "missing linux...". I failed to write the error down... /Lars -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
