Hello, I've already used WireGuard to connect to private networks and it's quite easy once you figure out how to set it up. (Most tutorials are outdated and haven't been updated, new ones haven't been written.) One thing that's really missing however is DNS support. All I can do now is connect to IP addresses. Names are not resolvable on the other side. If I add the "DNS" directive to my client configuration, it replaces the local DNS resolver and *all* lookups go to that server instead. This isn't working either because I'm on two local networks and each has its own local DNS server that can only resolve its own local names (and forward the rest to the internet).
Specifying both networks' DNS servers also fails because when resolving a name, one of them is chosen at random (and the other one isn't regarded) and then you won't be able to resolve some of the names some of the time. This is also very frustrating. And it wouldn't scale to multiple active tunnels. The solution I've read about is to set up a local DNS forwarder that can be configured so that it uses multiple servers and queries each of them and returns only a positive response. This way it could query both local LAN DNS servers and for local names, only one of them would resolve the name. This is a bit complicated to do if you're not permanently connected to a VPN, or if you move from one local DHCP network to another (like with a laptop). And it requires additional software, setup and configuration, and probably intensive maintenance and care. All of this makes WireGuard a pretty ugly alternative to OpenVPN where all of this already works. Despite all the disadvantages of OpenVPN. I'm asking if it's possible to integrate such a local DNS forwarder into the Windows client application. I imagine it would start up automatically once the first tunnel is activated. And it would replace the local system's DNS server setting for as long as it's active (like the tunnel-configured DNS server already does). And it would query the original locally configured DNS server and all configured DNS servers for the active tunnels. It would then be able to resolve local names and tunnel-remote names without any additional work on the user end. The user wouldn't have to perform many complex tasks upon activating or deactivating a tunnel. This would make WireGuard be as simple and productive as I believe it was intended to be (but isn't yet). This probably stops working as soon as other VPN software is used in parallel, but the current "DNS" setting has the same limitation, it's better than nothing and most of the time, you only run a single VPN software. Please let me know what you think of it. -Yves
