New
#60
About Windows' DNS Servers, just for your information folks!:
Windows 10 users switch to Google's Public DNS after bad ISP DNS setting blocks Windows Update:
Windows Update in Windows 10 is broken, but not Microsoft's fault - Windows 10 Forums
I restore to a 12/31/2018 build all is fine as soon as this KB4476976 is installed and I reboot the system is trashed.
What happens is that I have networking and can do nslookup to public and private no problem but can not ping anything by DNS, I can by IP however.
Here is an example of what I get.
I've never seen nslookup work but not ping, it makes no sense, but if I have no DNS the box is worthless, and restoring from a cold backup does nothing if the first time this KB4476976 is installed, and it always, is the system breaks again. I can not even use the restore point to get rid of it as the restore fails with an unknown exception which I can not look up as DNS is broken.Code:Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\Windows\system32> Get-DnsClientServerAddress InterfaceAlias Interface Address ServerAddresses Index Family -------------- --------- ------- --------------- Ethernet 4 14 IPv4 {1.1.1.1, 8.8.8.8} Ethernet 4 14 IPv6 {} Ethernet 3 21 IPv4 {1.1.1.1, 8.8.4.4} Ethernet 3 21 IPv6 {} Ethernet 6 16 IPv4 {} Ethernet 6 16 IPv6 {fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3} VMware Network Adapter V...1 19 IPv4 {} VMware Network Adapter V...1 19 IPv6 {fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3} VMware Network Adapter V...8 10 IPv4 {} VMware Network Adapter V...8 10 IPv6 {fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3} Bluetooth Network Connection 17 IPv4 {} Bluetooth Network Connection 17 IPv6 {fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3} Loopback Pseudo-Interface 1 1 IPv4 {} Loopback Pseudo-Interface 1 1 IPv6 {} PS C:\Windows\system32> nslookup www.google.com Server: UnKnown Address: 1.1.1.1 Non-authoritative answer: Name: www.google.com Addresses: 2607:f8b0:4006:800::2004 172.217.12.132 PS C:\Windows\system32> ping www.google.com Ping request could not find host www.google.com. Please check the name and try again. PS C:\Windows\system32>
Now tracert works and can get to remote sites through the proper gateway if I use IP, but not if I use DNS. I tried the solutions recommended to force DNS for example:
Without any change. I tried disabling all network adapters again not change, eveything works until this update then nothing works with DNS resolution.Code:Set-DNSClientServerAddress "Ethernet" –ServerAddresses ("10.120.25.1","1.1.1.1","8.8.4.4") Set-DNSClientServerAddress "Ethernet" –ServerAddresses ("2606:4700:4700::1111","2001:4860:4860::8888")
What can I do, I'm at my witts end having spent now 6 hours fighting and losing this battle, I simply can not think of what else to try or how to explain why this happens.
ERIC
After the KB4483235 (12/19/2018) update if my cursor drifted across the “New" on the context menu it would hang there for several seconds. Now, after the 12/30/2019 update, when I select “New” on the context menu it takes 5 seconds for the expanded menu to show. Weird Microsoft stuff.
Update installed for me and is working ok. I'm on BT Internet.