Hi.
After I update the latest vmin update recently, I noticed the server status on BIND server stop / not started.
I try to open the BIND DNS config page on webmin, and it shows:
The primary configuration file for BIND /var/named/chroot/etc/named.conf does not exist, or is not valid. Create it?
With this options:
Setup nameserver for internal non-internet use only
Setup as an internet name server, and download root server information
Setup as an internet name server, but use Webmin’s older root server information
Additional info, I still can do NSLOOKUP on a domain in this server.
Any help would be great on what to do next, thanks.
SYSTEM INFORMATION
Operating system CentOS Linux 7.9.2009
Webmin version 2.001
Virtualmin version 7.2
Usermin version 1.860
Authentic theme version 20.01.1:5
Previously this server was:
Operating system CentOS Linux 7.9.2009
Webmin version 1.999
Virtualmin version 7.1
Usermin version 1.854
Authentic theme version 19.99
and during this update, as like nyudoka said, we don’t find that error before, and we never had a problem. Until last night we upgraded to Webmin version 2.001 and Virtualmin version 7.2, the problem appeared.
Nope. We certainly check for such errors after every webmin update such as the server status page.
During the update to 2.001 which resulted the error of BIND as stated before, our monitor status also report:
Monitor on xxxx.com for 'BIND DNS Server' has detected that the service is uninstalled at 25/Sep/2022 15:40
also it produce error message on virtual server daily backup:
Copying records in DNS domain ..
.. domain not found!
There is no way we did not notice this kind of error if it happens before the update.
Nevermind. I think I still see an issue here for users who has never saved Webmin Bind module config.
Anyone with CentOS 7 needs to make sure that /etc/webmin/bind8/config file has the following directives added at the end of the file before installing Webmin 2.001 upgrade:
This also happened to my CentOS 7 after I installed the updates. I immediately noticed that BIND wasn’t running and all dns records were gone for each domain hosted. So I freaked out and restored the previous day back up of my VPS server on Vultr. Now my dashboard appears to be messed up and is missing a bunch of stuff.
You should check on /etc/webmin/virtual-server/config and /etc/webmin/system-status/config files and that they are in place and look correct.
Moreover, using UI you could check Webmin ⇾ Webmin Users: Edit Webmin User / Available Webmin modules / System Status / Module Access Control and see if all system information to show is selected.
Although, I don’t understand how you’re getting this issue if you’re restored from a snapshot. I would suggest to simply revert to the state before restoring from a snapshot and fix a Bind module issue as described on my previous comment.
All the config files are there, don’t know if everything inside them is correct.
Everything is selected under Available Webmin Modules. Unfortunately I can’t go back to the state before I restored from backup because I didn’t save that state. Should it be safe now to install the updates again after I applied your fix?
