OPNsense Forum

English Forums => 25.1, 25.4 Production Series => Topic started by: Lost_Ones on March 15, 2025, 03:29:33 PM

Title: 25.1 Unbound will not auto start after reboot - must be manually started
Post by: Lost_Ones on March 15, 2025, 03:29:33 PM
Hello,

I have noticed that when I reboot the system, I need to manually restart the unbound DNS service before DNS will work. I have also waited several services to see if it recovers, but not after 3-5 mins.  I have also noticed this behavior when CARP fails back over.   

From previous post that I have seen, many point to issues with VPN, however I do not have any of the VPNs enabled on my system.  I do have setting enabled to listed on all interfaces.

REview system general logs, I can see that the service is started    <118>Starting Unbound DNS...done.  but I dont see any indications that there is an issue.  I can see that Crowdsec fails, but I presume that is due to DNS not working.

Were there some settings changes that I many have missed with the new release?

Regards,
Title: Re: 25.1 Unbound will not auto start after reboot - must be manually started
Post by: cookiemonster on March 15, 2025, 11:20:47 PM
Perhaps Listening interfaces in Unbound is NOT set to all (recommended)?.
Title: Re: 25.1 Unbound will not auto start after reboot - must be manually started
Post by: Lost_Ones on March 15, 2025, 11:36:24 PM
Thank you for your suggestion, I can confirm that I am set to listen on all interfaces.

Regards,
Title: Re: 25.1 Unbound will not auto start after reboot - must be manually started
Post by: cookiemonster on March 16, 2025, 01:00:29 AM
OK. I don't use CARP so if that is related I couldn't tell.
However, I suggest looking at all the messages in the buffer from boot for clues.