OPNsense Forum

English Forums => 24.7, 24.10 Legacy Series => Topic started by: cgi2099 on November 20, 2024, 01:52:10 AM

Title: Unbound issues....
Post by: cgi2099 on November 20, 2024, 01:52:10 AM
Updated to the newest version of OpnSense and now am having issues with unbound.

If I change the unbound port to 5353 and reboot. There are still two processes running on 53

unbound  unbound    51797 7   udp4   *:5353                *:*
unbound  unbound    51797 8   tcp4   *:5353                *:*
unbound  unbound    51797 11  udp4   *:5353                *:*
unbound  unbound    51797 12  tcp4   *:5353                *:*
unbound  unbound    51797 15  udp4   *:5353                *:*
unbound  unbound    51797 16  tcp4   *:5353                *:*
unbound  unbound    51797 19  udp4   *:5353                *:*
unbound  unbound    51797 20  tcp4   *:5353                *:*
unbound  unbound    51797 23  udp4   *:5353                *:*
unbound  unbound    51797 24  tcp4   *:5353                *:*
unbound  unbound    51797 27  udp4   *:5353                *:*
unbound  unbound    51797 28  tcp4   *:5353                *:*
unbound  unbound    51797 31  udp4   *:5353                *:*
unbound  unbound    51797 32  tcp4   *:5353                *:*
unbound  unbound    51797 35  udp4   *:5353                *:*
unbound  unbound    51797 36  tcp4   *:5353                *:*
unbound  unbound    75119 5   udp4   127.0.0.1:53          *:*
unbound  unbound    75119 6   tcp4   127.0.0.1:53          *:*


This didn't happen before I updated. I need it off of 127.0.0.1:53 because that is where my AdGuard is.

Even did a reinstall with config restore, same thing happens.

Any thoughts?

Thank you,
Josh
Title: Re: Unbound issues....
Post by: cgi2099 on November 20, 2024, 03:37:24 AM
I can force close process 75119 and all is good. But on reboot I have the same problem again.

Any ideas?
Title: Re: Unbound issues....
Post by: appasquatic on November 20, 2024, 11:30:41 AM
Did you change the listening port to 5353 because you want to run DoT locally?
Title: Re: Unbound issues....
Post by: cgi2099 on November 20, 2024, 05:10:45 PM
Quote from: appasquatic on November 20, 2024, 11:30:41 AM
Did you change the listening port to 5353 because you want to run DoT locally?

Yes, has been working great for a couple of years : )
Title: Re: Unbound issues....
Post by: cgi2099 on November 20, 2024, 05:12:46 PM
Fix was to comment out the: "unbound_enable" line (also can be "local_unbound")

Located: /etc/rc.conf

Thank you some much @Mokkori-Man for the fix : )


*Edit, problem was two unbound instances running.
Title: Re: Unbound issues....
Post by: newsense on November 21, 2024, 03:00:09 AM
Leave Unbound running on 53, use Port Forwarding on the (V)LANs to redirect DNS queries to the new port you're running AGH on.