Unbound DNS not working anymore

[fre4ki]

Hey guys,

today i have some trouble with my Unbound DNS. It is not working anymore.

My OPNsense version is OPNsense 24.1.1-amd64

I have configured 2 Google DNS over TLS (port 853), IP 8.8.8.8 and 8.8.4.4 which was working well for a while.

After the issue i disabled DNS over TLS and checked the "Use System Nameserver" Box but there was no difference.

When i enter the Google DNS to my clients everything works as expected.

Any ideas what i can also check?

For now i'm using Dnsmaq, but i surely want to find the error.

Hope someone can help me.

Edit: What I see before the Unbound DNS / Statistics was also not loading.

Andy

[holunde]

Hi

I've encountered the same problem.
I'll get back to you when I have investigated further..

[JustMeHere]

I can't remember exactly what file it is, but sometimes the Unbound DB gets corrupted.  I've deleted it before and it's fixed this type of behavior.

[slackadelic]

Reporting -> Settings

Under "Unbound DNS reporting"

"Reset DNS Data"

I had to do something similar.

[Swtrse]

I nailed down the problem to a dependency with the DHCP service. When giving out new leases. The DHCP service seams to restart UnboundDNS to register the server's name for DNS resolve. Sometimes this seems to fail.

The solution that would work best in my opinion is some UnboundDNS API that could register and unregister names on the fly so that service restarts are not needed.
Or not so elegant to solve the service restart problem.

Oh and if UnboundDNS fails the Intrusion Detection fails too.

The error I get for UnboundDNS if it fails is in the general system protocolls.

Code: [Select]

/usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '37665''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 37665: No such process'I do not see realy more than that.