Post #3317852
2026-06-14 15:17 UTC
Having followed a tutorial, I could make #WireGuard wg-quick work on my #OpenBSD, but not without DNS query leaks, so I learned I must figure out #unbound - however, a noob like me can only seem to manage to fix configuration errors while unbound itself apparently won't start because of this (which I found out after learning there's more than one way to debug unbound - not elegant, imho):
[1781449588] unbound[95585:0] error: bind: address already in use
[1781449588] unbound[95585:0] fatal error: could not open ports
I figured I should add my VPN interfaces to unbound.conf, but other than that I'm still clueless what else do I need to add or delete.
Thanks for your patience.
Replies (2)
-
@subnetspider@mastodon.bsd.cafe 2026-06-14 15:56
@fionescu@mastodon.bsd.cafe The error sounds like as if another instance of Unbound is already running or some other software bound itself to port 53. You could check for other programs on port 53 with "netstat -atn". :)
-
@poes@sok.egois.org 2026-07-19 03:01
@fionescu@mastodon.bsd.cafe On #FreeBSD I usually add wireguard to the REQUIRED line in the unbound rc script so wireguard starts first. But on #OpenBSD you can just order services in rc.conf so wireguard runs before unbound. CMIIW