

I changed this setting as well for IP version 6.This post introduces a top VPN service named FortiClient VPN and offers detailed guides on how to download and install FortiClient VPN for Windows, Mac, Android, or iOS devices. So now the VPN has the lower number (higher priority) and is used first to resolve the DNS names. This number is higher than the value that VPN is using (25). To fix this, I modified the settings (Ethernet adapter > Properties > Internet Protocol Version 4 > Properties > Advanced) and changed from Automatic metric to a hard-coded value of 120. But when on wifi, the VPN had higher priority so it went out over VPN to resolve the DNS successfully. This meant that when on Ethernet, it was trying to resolve DNS locally, which failed. I found that my priority order (specified by the Interface Metric) was Ethernet, VPN, then Wifi. Using PowerShell command: Get-NetIPInterface | Sort-Object Interfacemetric.

It says that there's a priority order in which Windows will try to resolve DNS names.

But when connected via wifi it was resolving DNS names. I have a resolution! Thanks to each of you that replied and gave me clues of where to look!Īfter running some tracert and nslookup commands I found that while wired, I was not able to resolve DNS names, only IP addresses.
