Windows 10: Windows 11 Pro DNS resolution suddenly fails, IP Connectivity still works

Good afternoon! I've seen many posts around regarding Windows 11 and DNS seemingly stopped working. I'm having a similar issue however, I have validated that IP connectivity on my internal network, as well as to the Internet is still functioning. 1. OS: Windows 11 Pro - fully up to date 2. Intel WIFI AX 201 Adaptor HP Laptop running the lastest Intel driver from 8/20/2024 3. Asus ZEN WIFI AX RT8 mesh network running the latest firmwareTroubleshooting steps and remediation steps taken: 1. Opened the command prompt and ping several IP Address on my home network printers, gateway, o

:)

 

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?

 

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

I have fixed this problem permanently by manually setting the metric of my LAN connection to be higher (15) than the one windows assigns to my VPN (11).

This can be done two ways:

• Through the GUI: Network connections, Properties, TCP/IP v4 Properties, Advanced, Set Metric to 15;
• Command line: netsh int ip set interface interface="LAN CONNECTION NAME" metric=15

The effect is immediate and DNS lookups now go through my VPN as expected.

This works with Split Tunneling and is a permanent fix across reconnections and reboots.

Note that you could also change the metric of the VPN instead of the LAN connection, but this wouldn't be permanent as Windows resets the metric when the connection is established.

Depending on your environment, you may have a different default metric for your LAN and VPN connection. Simply adjust accordingly so that your VPN has a lower metric than your LAN connection.

I've cross-posted the answer to this problem on SuperUser: Windows 10 DNS resolution via VPN connection not working

 

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

Thank you ECC-Dan.

Changing the metric to 15 for TCP/IP v4 && v6 works. After ipconfig /flushdns, nslookup is pointing to the remote DNS server (it is DHCP scope setting for VPN clients) as opposed to local DNS server. So, from the angle of nslookup, it works ...

Additionally, I discovered another messy area on W10 is the Edge browser. I have a simple web page on the remote network for testing purpose. Edge DOES NOT work when I tried to open www.mydomain.local (it works in W7/8/8.1. I have to open it in IE !!

Nice to share my troubleshooting experience here.

Ben