Dns issue after windows update

Also, when I changed one of the workstations from an all dynamic config to a static config using 8. While at first I was relieved that my server was not at fault, it's odd that the non domain PC in the warehouse is the one with no issues All this points to a corrupt winsock registry, find a good Windows 10 computer and replace the winsock registry for that.

But my recommendation would be to reinstall from scratch after a backup. As you have mentioned that the non domain Pc is fine, this would point to a domain problem. Forget the PCs and start looking at the dns on your server. Your PCs should be getting dns from your server and their primary dns should be the Ip of your server. You can put google as secondary for failover if you like.

Your servers dns on the lan connection should be You saved the day! And so did Google DNS servers! Spectre X is untested so may be unsupported as of this document. Find a key named "SearchList", if it is a zero length binary then delete it and DNS lookups will be restored. I had this issue and searched for days finding no solution!

Removing this SearchList key resolved my issue, we can now start to upgrade devices to 20H2! FInally, I've been stuck on because at least 20H2 and 21H1 didn't work until making this change. After the change I ran the Network Adapter troubleshooter to reset all adapters and then I rebooted.

After reboot, DNS worked! Authorizing a DHCP server in workgroup. Skip to main content. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. When approx. Is Firefox, Chrome or any other alternate browser installed? How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. McAfee Security Center ver VirusScan I don't belive it expires.

Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. Wednesday, June 7, PM. If not correct it. Check the event logs. Time has been verified as correct. DNS Zone files verified as not corrupt. NIC's are configured as your graphic above. Uninstalling Windows update showed no difference. I'm thinking this is a DNS configuration issue. Please review graphic below: The folder "Elko" is a site location.