Am Sa, den 07.08.2004 schrieb Dino Nardini um 16:52: > I used yum to install bind* and caching-nameserver, accepting default > setups. All I can say is that rndc won't load a command channel with > bind-chroot installed... it tries but fails on both 127.0.0.0#953 and > ::#953 (ipv6 notation I believe?). Once I remove bind-chroot, it loads a > command channel just fine on 127.0.0.1#953. > > It should be noted that I'm not all that familiar with the workings of > bind-chroot or rndc. Any setup recommendations are welcome :) > > Cheers... Dino In your first posting you said you configured bind, now you are saying it did not work already with the default setup coming right after installation. It can't be both the case. So I asked for your specific configuration. $ netstat -tualpen | grep 953 tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25 9726 3736/named Running fine in chrooted mode, with default configuration as well after my customization. Did you remove the rndc key entry in /var/named/chroot/etc/named.conf? Any iptables rules active? You may read the bind documentation first, because DNS is a serious, essential service and proper working is needed for a lot of other things. Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.7-1.494.2.2smp Serendipity 16:54:46 up 3 days, 10:22, load average: 0.05, 0.05, 0.06
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
