Thanx a lot @Gertjan That was it. It was listening on port 953. Since I had not seen any configuration option in the UI I thought it was disabled.

[image: 1737050808671-685ef897-9dfa-4656-81a3-8cb04f4c40f8-image-resized.png] I am aware of the resolver interval, is there a way to bypass one url example imap.gmail.com always forward to 8.8.8.8 do not save in firewall dns namesever for reuse thus every time it gets the new ip address google has for the mail server, they change so fast the firewall can't keep up so the mail app at times says error after 5 mins it will resolve but that is unacceptable for modern use.

@myman said in Unbound: fatal error: Could not read config file: /unbound.conf: unbound-checkconf returns unbound-checkconf: no errors in /usr/local/etc/unbound/unbound.conf Runing " unbound-checkconf" will check the default /usr/local/etc/unbound/unbound.conf, a file that exists, but it is just a demo file. The real "unbound.conf", the one unbound for pfSense is using, is here/var/unbound/ Your unbound is restating every couple of minutes. If these restarts happen to often, then the start code can overlap with another startup. Then one of then can fail and you see the error shown. Disabling "DHCP registration" is one of the first things to try.