So I've been horsing around with the Luci-App-WireGuard a bit and I think I found a bug: it seems when editing the interface the "options dns x.x.x.x" is lost.
config interface 'wg0'
option proto 'wireguard'
option private_key '62lKu9HsDVbyiPenApnc4sfmSYTHOVfFgL3pyB+cBL4='
list addresses '1x.x.x.xxx/32'
option dns '1xx.1xx.xxx.x' <-- gone after changing key in luci
After some hours of troubleshooting, wiping and rebooting the router. I can definitely say I cannot get it working without the option dns in the wg0 interface.
uci set network.wg0.dns='x.x.x.x'
If I do not set it, it will default to 127.0.0.1 which in turn redirects queries to the DNS server in the WAN-connection. Which means I have DNS-leak. So I set it to ignore the advertised servers.
uci set network.wan.peerdns='0'
Where do I set the DNS server for WG? and how does this work with multiple WireGuard-connections if not specified in the connection network.wgX ?
So then I would advise you not to exclaim you've found a bug. I really donno how to better explain than others about Wireguard not having DNS. You merely route/allow the IPs of the proper servers thru Wireguard.
Otherwise, if your WG tunnel has a domain name, you have a chicken-or-the-egg issue where you need WG DNS before it can resolve the tunnel.
Perhaps you can look at threads that handle DNS leaks on VPN for more clarity.
My issue was the metric of the endpoint.
I will note that the disappearing setting does seem odd, though - since it exists.
I would fully document it for a bug report on LuCI.
