I find that quite often (several times week/day) DNS have stopped working due to Unbound being stopped as well.Under system->general->logfiles it seems like the reason is a segfault:<6>pid 57337 (unbound), jid 0, uid 59: exited on signal 11It has been like this since 23.7 and also now with 24.1.
I dont know if this is a unbound or quad9 issue.
Now Unbound sometimes (twice a day?) just stops resolving (response timeout) and it fixes itself after 5 minutes or so.
But my Unbound isn't crashing, just not always resolving a domain.
The only Unbound issues I've seen with Quad9 are some weirdness with DNSSEC and Quad9 returning different results per resolver.
Quote from: ksx4system on February 20, 2024, 01:18:39 amNow Unbound sometimes (twice a day?) just stops resolving (response timeout) and it fixes itself after 5 minutes or so.This issue persists on 24.1.2 Quote from: CJ on February 21, 2024, 09:07:20 pmBut my Unbound isn't crashing, just not always resolving a domain.It appears that it doesn't die per se for me too, it just stops resolving whatsoever for few minutes.Quote from: CJ on February 21, 2024, 09:07:20 pmThe only Unbound issues I've seen with Quad9 are some weirdness with DNSSEC and Quad9 returning different results per resolver.Neither Cloudflare's 1.1.1.1 nor ControlD at 76.76.2.0 seem to have this issue afaik.
I was just posting as a counterpoint because I've seen people commenting that the reason unbound isn't working correctly is due to DHCP, DoT, DNSSEC, the upstream resolver, DNSBL, etc. And I've had none of these issues dispute using all of those.
I will note that in the other thread, it seems that a lot of the people having issues with Unbound have a PC directly connected to OPNsense instead of through a switch. The only direct connects that I have are APs and they're always on, but even so, I've not had a problem when swapping them out.
Regarding Unbound temporarily not resolving, enabling the DNS reporting and higher log levels can help with troubleshooting that. But I would think a new thread would be in order as this one is about Unbound crashing and not just temporarily having an issue.
I find that quite often (several times week/day) DNS have stopped working due to Unbound being stopped as well.Under system->general->logfiles it seems like the reason is a segfault:<6>pid 57337 (unbound), jid 0, uid 59: exited on signal 11It has been like this since 23.7 and also now with 24.1. For my use on this box it is not critical , but rather an annoyance.The only thing that differs from the default is that I have enabled nearly everything on the blocklist under the DNBL drop down menu.In addition I have also added a URL to my own blocklist that resides on a remote server in the form of "http://example.com/blocklist.txt" - that connection has been difficult at times, but I imagine a non-existing file should NOT cause any issues with Unbound, but then again that is the only thing I can think of.As a side note - it would be great if it was possible to configure what to do if a service crash. (restart n-times before giving up, send mail, run a script (write to rs232 for example))