Multiple DNS "A" records being created for VPN clients
-
We have been using the official OpenVPN client for years and it's worked great however I'm looking at replacing it with the Viscosity client as it offers more features mainly easy scripting support. It has worked fine in my testing however I am running into a very annoying issue. When Viscosity VPN clients connect our Windows DNS server registers their local LAN IP in addition to the VPN IP. It also sometimes registers an IPV6 address as well. I'm am trying to figure out how to prevent this but so far have come up short. I was told by their support there was some way to only allow specific IP subnets in Windows DNS but I haven't found a guide explaining how to set that up. Maybe I just need to check the box to register OpenVPN connections in the firewall's DNS resolver? It is nice having them all on the windows DNS server but not if we keep having this issue.