Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
21.1 Legacy Series
»
Local DNS resolving is not working after restart of Wireguard
« previous
next »
Print
Pages: [
1
]
Author
Topic: Local DNS resolving is not working after restart of Wireguard (Read 2623 times)
JasMan
Full Member
Posts: 175
Karma: 9
Local DNS resolving is not working after restart of Wireguard
«
on:
May 23, 2021, 12:31:20 pm »
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.
Quote
2021-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.
«
Last Edit: May 23, 2021, 12:35:36 pm by JasMan
»
Logged
Duck, Duck, Duck, Duck, Duck, Duck, Duck, Duck, Goose
Greelan
Hero Member
Posts: 1028
Karma: 72
Re: Local DNS resolving is not working after restart of Wireguard
«
Reply #1 on:
May 23, 2021, 12:39:41 pm »
WG overwrites resolv.conf with the DNS servers specified in its config. Suggest you remove those
Logged
JasMan
Full Member
Posts: 175
Karma: 9
Re: Local DNS resolving is not working after restart of Wireguard
«
Reply #2 on:
May 23, 2021, 12:54:25 pm »
@Greelan: Yep, the WG config contained a wrong DNS server (typo). Solved. Thank you
Logged
Duck, Duck, Duck, Duck, Duck, Duck, Duck, Duck, Goose
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
21.1 Legacy Series
»
Local DNS resolving is not working after restart of Wireguard