Bind9 Security Update Broken

also virtualmin reports that BIND is disabled even though the service is up and running.

Same issue, but BIND is still is process list so it's running and just virtualmin for some reason doesn't recognize it.

Hmm, it looks like it was reported here that the BIND PID file location needed to be updated:

https://www.virtualmin.com/node/14570#comment-63791

For the cases above where Virtualmin is reporting BIND isn't running, does updating the PID file location help?

-Eric

Yes, updating PID according to instructuions in bugtracker helps, thank you! BIND is running correctly and Virtualmin clearly see it.

Can you restart the bind service? Stopping bind works fine. But starting... Not really... (Re)start via /etc/init.d/ works fine...

Syslog shows me the following error message:

Jun 7 09:04:10 www.domain.de named[24459]: none:0: open: /etc/bind/rndc.key: permission denied Jun 7 09:04:10 www.domain.de named[24459]: couldn't add command channel 127.0.0.1#953: permission denied Jun 7 09:04:10 www.domain.de named[24459]: none:0: open: /etc/bind/rndc.key: permission denied Jun 7 09:04:10 www.domain.de named[24459]: couldn't add command channel ::1#953: permission denied Jun 7 09:04:10 www.domain.de named[24459]: couldn't open pid file '/var/run/bind/run/named/named.pid': Permission denied

My System: Debian Lenny with Virtualmin GPL

I had the same issue. I run Debian Lenny and bind as chrooted. The new location of the pid file is (inside /var/lib/named chroot for my setup) /var/lib/named/var/run/bind/run/named/named.pid

So in the virtualmin bind configuration I had to change the location of the pid file to /var/run/bind/run/named/named.pid (without the chroot dir)

What seems strange to me is that the service script /etc/init.d/bind9 has the following lines

..
PIDFILE=/var/run/bind/run/named.pid
..
if start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/named \
        --pidfile ${PIDFILE} -- $OPTIONS; then
        if [ "X$RESOLVCONF" != "Xno" ] && [ -x /sbin/resolvconf ] ; then
        echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.named
        fi
        log_end_msg 0
    else
        log_end_msg 1
    fi
..

It seems as though the pidfile location set in /etc/init.d/bind9 is ignored

Hello I've got a similar problem: virtualmin reports that BIND is disabled even though the service is up and running.

I haven't bind8 , but bind9 yes , how can i do that virtualmin reports that BIND is enabled ?

I've got debian 5.04 and virtualmin pro.

I haven't any problems with bind9 , it's work fine and i've got no problem of dependecy with deb package.

Thanks

... Webmin > Servers > BIND DNS Server

Module Config > System Configuration

Default PID file location(s):

add to the list: "/var/run/named/named.pid" so it looks something like this:

/var/run/bind/run/named.pid /var/run/named.pid /var/run/named/named.pid

Save and then recheck the status screen. You may need to fake it by pressing the "Start" button against the service so WebMin figure it out.