BIND DNS Server marked as stopped in Webmin

In CentOS 6.3 Linux 2.6.32-279.1.1.el6.x86_64 BIND version 9.8.2, under chroot /var/named/chroot, the DNS server is consistently marked as down even if in fact is running. This happens both on the System Information page, where I get the play button, but when I click it, nothing happens, and on the BIND DNS Server page where in the right-up corner I keep getting Start BIND, also nothing happening if you click the link.

I replicated this twice, on a fresh install from the CentOS DVDs and with your script installer.



This is probably due to Webmin looking in the wrong place for the BIND PID file.

Where is the file on your system? It should be somewhere under the /var directory.

fakemoth's picture
Submitted by fakemoth on Fri, 07/20/2012 - 02:40

> locate

Wich one is the good one? BTW this gives all kinds of problems due to Virtualmin thinking Bind is not running, mainly when creating a new domain, and "Virtualmin is never ready for your system" :)

Those should actually be effectively the same file..

Could you attach the contents of the /etc/webmin/bind8/config file from your system?

fakemoth's picture
Submitted by fakemoth on Fri, 07/20/2012 - 15:01

/etc/webmin/bind8/config is not in the directory.

In /etc/webmin/bind8/ there are all the domains...

You mean the /etc/webmin/bind8/config file doesn't on your system?! That is really odd, as that is the primary configuration file for the BIND module.

fakemoth's picture
Submitted by fakemoth on Thu, 07/26/2012 - 10:14

Sry missed it the first time, there is a config file indeed, also the domains with an acl extension. But this problem is surely a bug, tried it the other day on a different (virtual) machine, a default server installation - the same!

fakemoth's picture
Submitted by fakemoth on Sun, 07/22/2012 - 04:07

stop_cmd=/etc/rc.d/init.d/named stop
start_cmd=/etc/rc.d/init.d/named start
auto_chroot=sh -c '. /etc/sysconfig/named && echo "$ROOTDIR"'

Can you try removing the line :

auto_chroot=sh -c '. /etc/sysconfig/named && echo "$ROOTDIR"'
fakemoth's picture
Submitted by fakemoth on Mon, 07/23/2012 - 02:23

Tried it - nothing happened, BIND seems down as before, and the little play button & links in webmin/virtualmin to start it doesn't do squad, even after a reboot and some updates to everything, so I put the line back in the config file as it seems it is not it.

I also removed the annoying Network Manager... because I don't like at all overwriting my files specially the hosts file? :)

fakemoth's picture
Submitted by fakemoth on Mon, 07/23/2012 - 03:31

Should I do a bug report also for this issue ? I'm getting a weird error on my primary Virtualmin server, a CentOS 5.8x64, when trying to add this one as a slave:

Failed to add server : flush_file_lines called on non-loaded file /etc/named.conf

Are the problems related maybe?

That could be related..

Is there any chance was could login to your system to see what is going wrong? If so, contact me directly at

I had a look, and it seems that the named configuration on your system is inconsistent - the chroot is not completely setup properly. If you like, I can correct it by turning off chroot mode?

fakemoth's picture
Submitted by fakemoth on Thu, 07/26/2012 - 01:33

Well... everything I read says that is not a good idee to have a BIND out of the jail, as it presents major security risks, so i rather have it setup this way. Can you maybe give me/us some hints? It seems to be working now, though the containts of a zone file is gone.

So this is a bug afterall, never had this kind of issues with previous CentOS releases...

Way back when, BIND did have some significant security flaws that were taken advantage of.

There have been very few issues in recent years though, and we frequently suggest not using the chroot. It unfortunately seems to cause more problems than it solves. As you're seeing -- there have been a lot of issues with it on CentOS 6.

The thing is that BIND runs as the user "bind" -- who doesn't have permission to do much other than DNS queries.

It's actually far more dangerous to install a web application on a website, than it is to run BIND outside a chroot.

Websites and SSH have become the simpler target these days -- the bots that used to roam the Internet looking to insecure BIND versions, they're typically either searching websites for out of date web applications, or banging on SSH looking for easy username/password combinations.

So if you keep having problems with the chroot setup, we'll continue looking into how to prevent those, but we really don't have problems suggesting someone run BIND without a chroot jail, and we'd have no problem running that configuration on our own servers.

In the meantime though -- it sounds like you were looking for some hints/ideas regarding your current setup -- did you have any specific questions that we can assist with?

fakemoth's picture
Submitted by fakemoth on Thu, 07/26/2012 - 10:04

I understand all of these and I completely agree with you to a point, but as I am still kind of a linux noob after all these years and books and servers and all kind of stuff, I developed a side-effect: extreme caution :) also called by others "the not talented, but working-hard admins paranoia" :)) I am the kind of person that gets panic atacks at night lol

So please can you try to make this work (no problem on my other server 5.8)? Almost everyone writes it is not a good ideea to run as root the DNS server (anyway it scares the hell out of me only when i see the user) so even If I have full confidence in your team (gave a password for the first time in my life to someone!) I tend to listen also to others.

Let me explain clearely how it works for us not so knowledgeable in linux: eveytime I'll have a problem, I'll suspect it's something wrong with BIND, being hacked and stuff, cause I'll know there is a chance. So why take it? Your software tends to ease my pains as an admin, so don't want to get any useless and pointless ones.

Enough wining in the Issues section :) ! Please tell me what to do: -wait for it, till you find a solution, and that you are willing to try and solve this; -or run it as default, because this is how the Webmin works and there is nothing more to do, and continue with the setup of the secondary server;

PS kind of a sick remark: now anyone registered here knows that all the users running Webmin and CentOS 6 are not chrooted, and their number will grow.

I would recommend turning off chroot - in my opinion the security benefit is tiny, while the operational overhead is substantial.

hey jamie this is happening to me again (it has been running great ever since you helped out)....

My server was shut down due to a power outtage and then of course it is showing bind as not running when it actually is.


Hi warren0728 -- it looks like you have an existing support request regarding that issue... can you follow on that request? That'll make it easier for us to provide assistance. That request is here:


no prob wasn't sure which thread would be better!