[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 17:01:

> Caused by the fact that the -t option is specified in 
> /etc/sysconfig/named (which is passed
> to the named daemon on the commandline for chroot to another directory).
> 
> After removing that line from that file rndc was able to build the 
> socket succesfully on
> l27.0.0.1:953.

> jan

So your bind no longer runs chrooted?
--> ps axuwww | grep 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?

My bind-chrooted service still runs on an FC1 host without any glitches.

Alexander


-- 
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 19:27:49 up 2 days, 1:24, load average: 1.31, 1.38, 1.43 
                   [ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - 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]