Windows 10: OpenVPN connected. No DNS resolution

ISSUE

OpenVPN is getting connected. But sites are not resolved


DESCRIPTION

Our organization have an OpenVPN Neth server with limted server and site access. Some Windows 10 Pro machines are able to access the servers and sites after connecting to the VPN server, some are getting connected but have DNS resolution issues. We are not able to access anything from those machines. There are no issues with other OS too.


ERROR

ERR_NAME_NOT_RESOLVED


WHAT I HAVE TRIED

• Tried access with different web browsers.
• Cleared browser cookies and data
• Changed DNS in network adaptor settings
• Flushed DNS

Are there any fixes for this issue?

:)

 

I can connect to VPN using openvpn but I can't get internet

I cannot ping google.com or bing.com while connected to my VPN or access any
website. I can connect to my VPN, but I do not have internet access while connected.

Below is what I have tried

• Disabling windows firewall and comodo firewall
• Setup my DNS routing to Cloudflare 1.1.1.1 and Google Public DNS 8.8.8.8
• Uninstalled my wireless driver then installed it again as administrator then uninstall openvpn client and install it again as administrator
• Make the openvpn client run as administrator
• Change the interface metric for my wifi adapter to 15 or 350
• See below

How can I make my vpn connection have internet. I am using Windows 8.1 64 bit. The VPN connection works on my android phone.

 

Microsoft Surface 3 cannot connect to web sites ... no DNS resolution

Try using DNSjumper (free) and see what it says when it tries to list your available DNS's.

That you have upgraded successfully indicates there is a configuration or 3rd party-related problem that is not overridden by the upgrade. Your services should be set to default.

Try resetting your Internet options:




Have you ever changed your Hosts file or used any utility that may have done so? Check it is default.

What security software are you using?

Can any other device use the same connection successfully?

 

Win 10: DNS resolution of remote network via VPN connection not working

Changing the metric worked for me, but my situation was a little different:

DNS resolution with my VPN had been working flawlessly with Win10 (first with Preview, then with RTM, always kept up-to-date) using Dell SonicWALL NetExtender (currently version 7.5.223)

Then this morning DNS resolution with my VPN stopped working suddenly. I hadn't explicitly made any changes or installed any updates or software. Perhaps an automatic update broke things.

Though the VPN still connected fine, and though the interface binding order HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LanmanServer\Linkage\Bind was properly updated on connection of the VPN (i.e. the VPN's interface was added to the top of the list),
NSLOOKUP would use my LAN's DNS servers rather than the VPN's DNS servers. The VPN client was however showing properly-configured DNS servers.

In my case I was unable to open TCP/IPv4 properties for the "SonicWALL NetExtender" interface: the "Properties" button was displayed as being active, but clicking on it did nothing / did not open a properties dialog.

So instead I went to TCP/IPv4 properties for my Ethernet interface, clicked Advanced, and unchecked "Automatic metric", and assigned an arbitrary metric of 100.

After doing this DNS resolution once again works properly: When the VPN is connected the VPN interface's DNS servers are used. When the VPN is not connected, the Ethernet interface's DNS servers are used.