[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Core 2: rndc failure to communicate

Am Mo, den 24.05.2004 schrieb Jan Houtsma um 23:19:

> >So your bind no longer runs chrooted?
> >--> ps axuwww | grep named

> root:/var/log> ps axuwww | grep named
> named     2116  0.0  2.0 38640 4024 ?        S    May22   0:00 
> /usr/sbin/named -u named

As I expected you made it running non chrooted. The chroot directory is
set in /etc/sysconfig/named.

> >Can you post your /etc/sysconfig/named configuration file as well the
> >/var/named/chroot/etc/named.conf file - without the zone file entries?
> >Do you have the /var/named/chroot/etc/rndc.key file? How did you
> >configure your bind?

> Oh shoot. I get it now i think! I had to put named.conf and rdnc.key 
> files under the chroot directory???? I still had them under the /etc hiearchy. That explains 
> it! And now it works!

Yes, if you want to run bind chrooted all the config, zone, log and
other needed files have to be inside the chroot directory, because the
chrooted bind can not see anything outside.

> jan


Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2188.nptl
Sirendipity 00:15:11 up 2 days, 6:11, load average: 0.38, 0.35, 0.54 
                   [ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ]
             my life is a planetarium - and you are the stars

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]