I may have lost my mind here but we ran standard updates in virtualmin and it updated the webmin package to 1.675-1. At that point we got errors in the Named server that it would not start. When clicking on the named server to see the hosts we were prompted with 3 options essentially asking how we want to setup the config. Unfortunately I did not write these down but we did not want to commit to any in fear it would wipe out all of the zone files we currently had in place and mess with the config. Instead we quickly ran a yum downgrade webmin and the package returned to version 1.660-1 and the problem went away. Any help on this would be appreciated. Note that this is on CentOS 6.5 and the package is coming from the virtualmin-universal repo according to yum list updates command.
This could be due to a change in the way BIND chroot handling is done in Webmin 1.670 and above. Try going to the BIND module, clicking on Module Config, and setting the "Chroot directory to run BIND under" to /var/named/chroot . Or if it is already set, change it to "None".
''
Sounds good. Going to try this tonight after running the update again. Fingers crossed.