pfSense » pfSense Plus

Yaroslav Semenenko wrote:

Hello,

I have Netgate 2100.
Unbound service is needed to restart sometimes due to it could not resolve public domain name.

Thanks,
Yaroslav

I'm having the same issue. I've used the Service Watchdog to restart it when it fails. But even this sometimes doesn't work. My unbound will sometimes fail when my VPN's are coming online and Service Watchdog won't notice it right away so internet traffic fails.

This unbound not restarting has been an ongoing issue for a while now I've seen in my builds.

I use the Netgate 1100 with 23.01-RELEASE and can second that unbound from time to time stuck. Only restart the service will help. When I can help to provide more information, I like to do. It is a really annoying problem for me.

Yaroslav Semenenko wrote:

Hello,

I have Netgate 2100.
Unbound service is needed to restart sometimes due to it could not resolve public domain name.

Thanks,
Yaroslav

I use 23.01- RELEASE as well. I was facing the same issue. Each time Pfblocker cron job used to run (Pfblocker & resolver both running on Python mode) DNS resolution used to break when the database was assembling.

Upon restarting my PfSense I used to get FATAL error messages in notification.

I tried to restart unbound from SSH and it was giving the same PHP Fatal errors.

I am practically unable to use the DNS resolver. I am unable to resolve netflix and many other domains unless I enable the forwarding mode in DNS Resolver.

Hope these issues get resolved at the earliest.

Post this in the forum it could be you are not using the correct settings and ACL's for unbound.