After updating to 24 this evening Dnsmasq (my default) and alternatively, Unbound are no longer able to resolve WAN locations.
I worked through fixing the gateway issue I was having (like some others), but this DNS issue has me stumped. Of course, if I bypass the local DNS and insert an external DNS IP in the DHCP settings it works.
Any ideas what is causing this and how to fix the issue?
Thanks!
I leaned into dnsmasq a while ago because it seemed to have (actual) support for integrating with the names sent in DHCP registration -- never could get unbound to do so -- and as of the latest 24.x.x series I'm now seeing dnsmasq crap out several times a day. It's running, port is open, it doesn't answer queries.
Just a data point for now.
I'll enable debug logging soon.