DNS Unbound and DNSMasq Turning off Randomly

[eminent]

Good morning,

I am currently on  Version: 21.7.r_228,  I moved to Development because of this issue but its happening on both Stable and Development. Currently running Unbound every morning at 4 AM Eastern, my DNS just stops working.  As far as I can tell there is no crashes in logs, just at 4 AM everything stops resolving. The only way I can get it back up and running is 

I thought I would be able to resolve this by scheduling via a Cron Job to reboot the system at 4:01 AM Eastern.  But that still did not fix the issue.  So I tested utilizing DNS Masq instead of Unbound, and I have the same issue.

In order to get everything back up and running I have to disable the DNS Service I am running, allow upstream to overwrite DNS, reboot then enable my DNS Service of choice then disable upstream.

Anyone have advice of where I could look either in logs or anyone experience this before?

Thank you.

[franco]

Check the individual log files, check "dmesg" console output. A part of the system will tell you why the service stopped / wasn't starting. However, not a lot of things changed in Unbound / Dnsmasq so it's more of a question about your setup / configuration than code changes per se.


Cheers,
Franco