The test takes only a few seconds and we show you how you can simply fix the problem. Just to be sure, I switched back to Tunnelblick to see if the fact that this didn't work may be due to the domain being the same on both sides. offers a simple test to determine if you DNS requests are being leaked which may represent a critical privacy threat.
I just changed it on one of the network in the router's settings, rebooted it to trigger new DHCP leases, and voilà ! I can now directly ping DNS aliases for stations located on both sides of the VPN and they all respond ! In my case, the domain used to be the same on both of my networks ("lan"), so this didn't work at first. It turns out that this client has a setting called "Split DNS", which allows to use both the server's AND the client's DNS, depending on the network's domain. I was looking for other OpenVPN clients on macOS (I was using Tunnelblick), just out of curiosity, and came across Viscosity. I just found a solution completely randomely ! I figured I would share it.
Viscosity vpn dns windows 7#
Requirements Operating System Windows 7 SP1, 8 & 10. If you prefer a free alternative, pick another software/protocol on our setup page.
Viscosity vpn dns software#
Recommendations Paid Software Viscosity is a premium software and requires payment. Is there a way to configure OpenVPN so that this works ? Or maybe I'm completely missing something here. It’s the most stable OpenVPN client on Windows. I didn't even managed to find any similar case, even though this seems to me like a pretty important use case. I've spent hours looking for a way to fix this, without success. That doesn't seem to be the case under macOS. Then the client seems to use both the real and tun interface and therefore manages to reach both DNS servers and use all the aliases.
This seems to be more due to the way the DNS entries are used than the way my setup is configured, but I don't face this problem with a Windows client, since the tun interface seems to get its own DNS entry (the VPN server's IP that's been pushed). This behavior seems correct because if I change the order of the DNS entries by putting the local one first and the VPN one after, the result is reversed : I can use local aliases but I can't use the remote ones anymore. If in Hostname or IP Address I enter my DDNS (), the client cannot connect via Viscosity on the MACbook. Code: Select all ping: cannot resolve my_alias: Unknown host Hi, I downloaded the OpenVPN VM (Ubuntu base), configured the server via GUI and I am able to connect through the client.