Re: Problems with chrooting bind 9.2.0
Thursday, February 14, 2002, 2:14:30 PM, Michael Wood wrote:
>> 2) copying it to /chroot/named/etc/bind
> i.e. /chroot/named/etc/bind is a directory containing the file
> rndc.key?
> This should work. What do the logs look like now?
Okay, it looks like this now:
/chroot/named/etc/bind consists of:
---schnipp---
-rw-r--r-- 1 named named 837 4. Feb 08:02 localtime
-rw-r--r-- 1 named named 2960 17. Feb 12:15 named.conf
-rw-r----- 1 named named 180 17. Feb 12:05 rndc.conf
---schnapp---
My named.conf:
---schnipp---
// rndc-key
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
---schnapp---
And my rndc.conf:
---schnipp---
options {
default-server localhost;
default-key "rndckey";
};
server localhost {
key "rndckey";
};
key "rndckey" {
algorithm hmac-md5;
secret "here_is_my_secret_key";
};
---schnapp---
After starting bind9 daemon.log tells me:
---schnipp---
Feb 17 19:11:37 iridium named[194]: /etc/named.conf:48: \
couldn't find key 'rndckey' for use with command channel 127.0.0.1#953
---schnapp---
And finally:
---schnipp---
iridium:/chroot/named/etc/bind# /etc/init.d/bind9 stop
Stopping domain name service: namedrndc: \
neither /etc/bind/rndc.conf nor /etc/bind/rndc.key was found
---schnapp---
So, do you have any further ideas?
Regards
Marcus
--
Fickle minds, pretentious attitudes
and ugly make-up on ugly faces...
The Goth Goose Of The Week: http://www.gothgoose.net
Reply to: