Local DNS resolving is not working after restart of Wireguard

Started by JasMan, May 23, 2021, 12:31:20 PM

Previous topic - Next topic
Hey,

When I restart the Wireguard service, OPNsense is no longer able to resolve DNS names by itself. The LAN clients are all fine, only OPNsense can't resolve e.g. FQDN aliases.

Quote2021-05-23T12:21:01    unable to resolve download.qnap.com for alias WAN_QNAP_Download

I've to restart the appliance to resolve the issue.

I'm using Unbound as DNS resolver. It's listening on a loopback adapter, which address I have configured in the DHCP DNS server options for the clients as well as in the general settings of OPNsense (System: Settings: General)

I can remember that there was a similiar issue with OpenVPN, but I can't find the thread/issue on Github.

Any recommendations?

EDIT: Found out that saving the genereal settings of OPNsense again also solves the issue.
Duck, Duck, Duck, Duck, Duck, Duck, Duck, Duck, Goose

WG overwrites resolv.conf with the DNS servers specified in its config. Suggest you remove those

@Greelan: Yep, the WG config contained a wrong DNS server (typo). Solved. Thank you :)
Duck, Duck, Duck, Duck, Duck, Duck, Duck, Duck, Goose