Problems with chrooting bind 9.2.0
Dear all,
first I would like to apologize for my English as I am not a native
speaker.
I'm using Debian Woody with the current bind 9.2.0 and I'm trying to put
it in a chroot jail. I downloaded Scott's "Chroot-BIND HOWTO" and it
worked very well except for a few small things.
The chroot jail is set up, the files are moved and starting bind works.
:-)
The daemon.log tells me:
Feb 13 17:04:39 iridium named[1525]: loading configuration from \
'/etc/named.conf'
Feb 13 17:04:40 iridium named[1525]: no IPv6 interfaces found
Feb 13 17:04:40 iridium named[1525]: listening on IPv4 interface \
lo, 127.0.0.1#53
Feb 13 17:04:40 iridium named[1525]: listening on IPv4 interface \
eth0, 192.168.0.1#53
*a* Feb 13 17:04:40 iridium named[1525]: none:0: open: /etc/bind/rndc.key: \
file not found
*b* Feb 13 17:04:40 iridium named[1525]: couldn't add command channel \
127.0.0.1#953: file not found
Feb 13 17:04:40 iridium named[1525]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1
Feb 13 17:04:40 iridium named[1525]: zone 0.168.192.in-addr.arpa/IN: loaded serial 2002020901
Feb 13 17:04:40 iridium named[1525]: zone home/IN: loaded serial 2002020901
Feb 13 17:04:40 iridium named[1525]: running
*a* and *b* confuses me a little. Although rndc.key is in the chrooted
/chroot/named/etc/ I get this error message (in addition
"/etc/init.d/bind9 stop" tells me "Stopping domain name service: \
namedrndc: neither /etc/bind/rndc.conf nor /etc/bind/rndc.key was \
found".
Regarding *b* the shown message confuses me even more because I have
never had it before chrooting bind.
Do you have any ideas?
Thanks in advance,
Marcus
--
Fickle minds, pretentious attitudes
and ugly make-up on ugly faces...
The Goth Goose Of The Week: http://www.gothgoose.net
Reply to: