Mike H

Sorry for the delay. I'd just restarted the server so there was no info.. The results are below. I've been restarting named on a cron job every 6 hours, and just now it went again, so it's lasted almost 5 days this time. SELinux is disabled: sestatus SELinux status: disabled Apr 20 16:21:41 webhost systemd[1]: Started Berkeley Internet Name Domain (DNS). -- Subject: Unit named.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel...

Sorry for the delay. I'd just restarted. The results are below. I've been restarting named on a cron job every 6 hours, and just now it went again, so it's lasted almost 5 days this time. Apr 20 16:21:41 webhost systemd[1]: Started Berkeley Internet Name Domain (DNS). -- Subject: Unit named.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has finished starting up. -- -- The start-up result is done....

Apologies. CentOS Linux 7.7.1908 x64 BIND version 9.11 Webmin version 1.942 Usermin version 1.791 Virtualmin version 6.09

Thanks for the reply. It's fully patched, and is a VPS provisioned a month ago. It gets rebooted weekly also. It has 16GB ram and only one small website is hosted on it. I've not found anything in logs but Googling shows this is quite a common problem with no apparent solution.

Hi, I have a webmin/virtualmin setup with one website on. Every few days (it's random) the webites will drop offline due to NS records not working, and webmin also drops offline unless accesed via IP. Logging into SSH and restarting named service resolves the issue. Short of restarting the named service on a cron, has anyone any ideas at all? This is impacting live sites frequently. Thanks

Hi, I have a webmin/virtualmin setup with one website on. Every few days (it's random) the webite will drop offline due to NS records not working, and webmin also drops offline unless accesed via IP. Logging into SSH and restarting named service resolves the issue. Short of restarting the named service on a cron, has anyone any ideas at all? Thanks