found bugs?

Hi Jamie
can you look at http://www.virtualmin.com/node/21577
I believe there are still some issues with virtualmin and centos 6
Especially the last post from Locatus
thank you

Status: 
Closed (fixed)

Comments

It sounds like the issue seen in the thread there is that BIND wasn't being restarted when adding a new domain on CentOS 6.

After restarting BIND, it worked okay for them.

This is the information Locutus provided:

Reason for the REFUSED was that Virtualmin failed to restart/reload BIND to apply the newly created zone. After a manual restart, the zone resolved correctly.

We then changed the command Webmin uses to apply BIND changes from "Stop and restart" to "Command: rdnc reload", after setting up RNDC. With that change, Virtualmin then succeeded in applying BIND changes.

I just wanted to confirm that I'm seeing this same behavior on my CentOS 6 test system using Webmin 1.583.

Adding a new domain isn't restarting BIND -- so the zone isn't available until BIND is manually restarted.

Additional info: The issue seemingly applies to not just creating a new domain, but all activities involving BIND, i.e. turning on/off the BIND feature for an existing domain. Which is to be expected, I suppose, since the same bit of code is probably involved in both cases.

Ok, I see the issue here - the wrong restart command for BIND is being used on CentOS 6.

We will add a fix for this in Virtualmin 3.91, but the work-around till then is to edit /etc/webmin/bind8/config and change the line :

restart_cmd=restart

to :

restart_cmd=/etc/init.d/named restart

Actually you don't even need to edit a file for that... The Webmin GUI itself has, in the "Module Config" part of the BIND Module, an option to choose the restart command. No Webmin restart is necessary then either.

That also works ... And effectively updates the same file.

Automatically closed -- issue fixed for 2 weeks with no activity.