Unbound stops resolving

[satish]

I am using DoT, with quad9, and I made sure to have no DNS servers in system > settings > general.
I have quite a few blocklists which I use, and while everything is working it all seems fine.
I randomly face issues where unbound just stops resolving /crashes , however, in the logs , I can not see anything related to a crash. Because this kept randomly happening, I run BE on my main gateway and  I created a secondary VM with opnsense for a secondary DNS.

[ThyOnlySandman]

Probably unrelated as my unbound wasn't crashing the service but I was having constant unreliable DNS resolution back on 24.1.x.  Both internal 53 + external DOT 853.  DNS resolutions would randomly fail and then try second later and work.  Constant SERVFAILS.

The fix I found finally was interfacing binding.  For years I had unbound both "Network Interfaces" + "Outgoing Network Interfaces" on specific interfaces.  Upon setting both to ALL interfaces (0.0.0.0) all my unbound problems went away.  Unbound ACLs to control access.  Finally returned to being reliable.

Probably not your situation but worth a check if your not binding unbound all interfaces.

(Also had numerous other binding issues.  Like Webui not running at boot due to specific MGT interfaces and redis also not starting when not set on LAN interfaces.  Believe either changes to freebsd itself or IPv6 work being done on Opnsense - Specific interface binding became quite problematic if not set on ALL within last year.)