Windows 10: DNS problems on Win 10

Hi all,
I have Internet problems since I upgraded from Win 7 to Win 10. Sometimes I don't have Internet when I turn on my PC & it seems has problems with DNS when I use diagnostic tool & it's unable to repair it, until I don't reset my router.
Anyone else having the same problem?

:)

 

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

I can confirm that I also have the issue. To resume:

- Windows VPN does not try to resolve hostnames with the remote DNS, with or without split-tunneling enabled. It always uses the DNS defined on the local network card.

- Issue is new to Windows 10, Windows 8.1 was working correctly with the exact same VPN configuration.

- Split-tunneling has nothing to do with the issue as the local DNS setting is used in both scenarios to resolve hostnames which is wrong. Hostnames should be resolved by the remote DNS. By the way, there is a bug in the VPN GUI of Win 10, it is not possible
to access the dialog to change the split-tunneling configuration. It can only be done through PowerShell.

- Even if IPV6 might be involved in the issue, I have never touched the default IPV6 config under Win 8.1 and DNS always worked correctly. It should be the same with Win 10.

- With nslookup we can clearly see that it uses the DNS of the NIC and not the one pushed by the VPN. nslookup under Win 8.1 uses the VPN defined DNS.

Microsoft, please address this issue as this is a showstopper for enterprises using the integrated Windows VPN. It is broken!

UPDATE 1: problem is actually a bit different than what I thought, DNS resolution works IF you don't use the FQDN of the internal machine you want to reach. The funny thing is that "ping mymachine" will return as a result "mymachine.mycompany.com".
But trying to ping "mymachine.mycompany.com" does not resolve since it uses the locally defined DNS. So the problem is with the DNS filter, it does not use the DNS suffix search list to decide where the DNS query should be sent.

UPDATE 2: problem is not specific to Windows VPN, SonicWALL NetExtender VPN has the same issue. So it's the DNS resolver which is common to all VPNs that has the issue.

UPDATE 3: DirectAccess is also not working, also seems related to the DNS issue. Looking at the DirectAccess Troubleshooter log there are various unresolved hostname errors.

 

Ethernet not stable since win 10 upgrade

I was having trouble after the Win 10 AU. Most of the errors pointed at DNS server problems.

IPCONFIG /ALL showed I was using the comcast DNS servers.

I switched over to the Google DNS servers and everything cleared right up, 8.8.8.8 and 8.8.4.4 for IPv4 service

Go to the properties of the network adapter, IP V4 and manually enter these addresses in the DNS field.

 

Under properties\Power Management for your network card do you have Allow PC to turn off this device? If so, uncheck those Power setting boxes and see if that helps.

 

I certainly think there are serious DNS problems. I have installed the release via upgrade from 7. Occasionally when surfing (Edge or Chrome) i get a long delay, then "Webpage not Available," frequently followed in a few seconds with the requested page.
I have switched to fixed DNS server addresses, and the situation seems to be improved.