Unbound DNS Issues after clean install of 24.1.3_1

[jshiflet]

I'm having a really strange problem with a new install/config of OPNsense 24.1.3_1. I've configured Unbound DNS and left it listening on my LAN interface UDP port 53. I've also enabled the "Do not use the local DNS service as a nameserver for this system" option under System > Settings > General.  I've also enabled the Unbound DNS statistics reporting under Reporting > Settings. Whenever I do a query against the new install using a tool like dig or doggo, and manually specify <LAN-Interface-IP>:53 as the server, I do actually get responses back, HOWEVER, those queries are not being logged by Unbound DNS. I've even tried turning on all the query and response logging, and turned up the logging levels in Unbound DNS, and it clearly isn't actually acting as the resolver.

Now, here's where I know there's some sort of problem: if I change the listening port of Unbound to something like 153 and repeat a manual query of IP:153 with dig or doggo, I can see that response in the statistics log, as well as in the actual Unbound log as well.

I can also completely stop the Unbound service and run queries against the firewall and they still resolve.

Is there some other resolver service that runs that's not Unbound on a new install that listens on port 53 that I'm not seeing anywhere? Or could it possibly be that there's some sort of bug here?

[Saarbremer]

It seems as if there is something else on port 53.

Can you open a shell and run

Code: [Select]

sockstat -l | grep udp | grep :53
to check which services are actually listening and where. Furthermore, is there any firewall/nat rule regarding port 53 doing quirky things?