In a previous submission, my 'localhost' file was overwritten by mistake. That would prevent 'localhost' to be resolved in 127.0.0.1 Apologies for the mistake. Maurizio
Created attachment 3889 [details] fixed ${FILESDIR}/localhost file
Created attachment 3895 [details] fixed named.rc6 NB. This is a trivial problem that cames from previous releases of named.rc6. I've just noticed and fixed it. in checkconfig() OPTIONS get redefined to add the CHROOT stuff to the OPTIONS already setted in /etc/conf.d/named when the restart() is executed. (i.e. stop() and start() ), OPTIONS is already defined and will result in a duplicate. example sexybit Desktop # /etc/init.d/named restart * Stopping named... [ ok ] * Starting chrooted named... [ ok ] sexybit Desktop # ps ax | grep named 6222 ? S 0:00 /usr/sbin/named -u named -n 1 -t /chroot/dns -t /chroot/dns 6225 ? S 0:00 /usr/sbin/named -u named -n 1 -t /chroot/dns -t /chroot/dns the new named.rc6 version doesn't use OPTIONS in checkconfig() and the start() has a redefined start command: start-stop-daemon --start --quiet --exec /usr/sbin/named -- -u named \ -n $CPU $OPTIONS ${CHROOT:+-t $CHROOT} Maurizio
seemant, I've reassigned this bug to you since Ben told me he's quite busy with his work atm and these two files need to be submitted as soon as possible or we'll get new BIND user claiming their nameserver do not resolve 'hostname' into the loopback address. Thanks :) Maurizio