Advertisement

Windows DNS client stops working after sleep

When a PC wakes and name lookups fail, the problem may be DNS, not the internet. This article shows how to confirm the failure point, check adapter power settings, and try the safest fixes first before you blame the router or VPN.

Windows 8 min read

If Windows wakes from sleep and name lookups stop working, the problem is usually not the whole internet connection. It is more often a sleeping network adapter, a stale DHCP or DNS lease, a cached DNS entry, a VPN or security filter, or router behavior after resume. Start by proving whether it is DNS-only, then try the safest reversible fixes first.

What you see after sleep

The usual pattern is this: the PC wakes, Wi-Fi or Ethernet looks connected, but websites by name do not open. If a site works by IP address but not by name, DNS is the part that failed. If both name and IP fail, it is not just DNS, and you should stop treating it like a cache problem.

This is easy to misread because Windows can show a normal-looking network icon while the adapter, lease, or resolver path is still half-broken. In practice, I treat that as a sign to test the connection before I change anything.

Before you start

  • Use the exact adapter you normally use after sleep: Wi-Fi or Ethernet, not both at once.
  • If you use a VPN or third-party security suite, be ready to disconnect or pause it for a test.
  • If the problem only appears after sleep, test it right after wake before rebooting. A reboot can clear the state and hide the real cause.
  • If you are on a managed work PC, some adapter or VPN settings may be controlled by policy, so you may not be able to keep every change.

The most likely sleep-related causes are adapter power saving, a stale DHCP renewal, DNS cache entries that no longer fit the live network, VPN or security filters, and router behavior after resume. One report on a Windows 10 machine found that reinstalling the NIC driver and clearing the setting that lets Windows put the adapter to sleep resolved the issue.

Try the safe fixes first

  1. Confirm that the failure is DNS-only.

Open a site by IP address if you already know one, or run nslookup against a name you trust. If the IP works and the name does not, keep going with DNS checks. If the IP also fails, the network path itself is the problem.

Command Prompt
nslookup www.example.com

If nslookup shows the server being queried and then times out, that points to the resolver path rather than the site itself. If it succeeds, DNS is probably not the active failure.

  1. Disconnect and reconnect the adapter.

Turn Wi-Fi off and back on, or disable and re-enable Ethernet briefly. This is the quickest way to force Windows to re-handshake after sleep without changing settings.

  1. Flush DNS if the adapter is clearly alive.
Command Prompt
ipconfig /flushdns

This helps when the local cache is stale or out of step with the current network. It will not fix a network adapter that did not wake cleanly, and it will not repair a bad VPN filter.

  1. Renew the lease if the link is up but name resolution is still wrong.
Command Prompt
ipconfig /release
ipconfig /renew

If this works, Windows gets a fresh DHCP lease and may also pull a fresh DNS server. If it fails, the problem is lower than DNS cache alone, and you should look at the adapter, driver, or router.

  1. Disconnect any VPN and retest.

If DNS starts working as soon as the VPN is off, the VPN client or its filter is part of the failure path. That is a much more likely explanation than a broken public DNS server.

  1. If you use security software with a network filter, test with it disabled only long enough to compare behavior.

Some security suites hook name resolution or traffic filtering and can leave things broken after resume. If the issue disappears when the suite is off, that is a strong clue that the conflict is in that software rather than Windows DNS itself.

Check the adapter, DHCP, and DNS settings

The most useful checks are the adapter power setting, the live IP configuration, and the DNS server Windows is actually using.

  1. Open the adapter properties.

Use the classic adapter list or Device Manager, then open the properties for the Wi-Fi or Ethernet adapter.

Settings path
Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings
  1. Check power management.

In the adapter’s device properties, look for the power management tab. If there is a box that lets Windows turn off the device to save power, clear it. That setting is a common cause of wake-up failures because the adapter may not resume cleanly.

  1. Inspect the live IP and DNS data.
Command Prompt
ipconfig /all

Look for the active adapter, the IPv4 address, the default gateway, and the DNS servers. If the DNS server shown there is missing, wrong, or looks stale right after wake, the problem is more likely DHCP renewal or router behavior than the DNS cache.

  1. Test name resolution directly.
Command Prompt
nslookup www.example.com

If the lookup fails but ipconfig /all shows a normal address and gateway, the network link is up but the resolver path is not. If the first line of nslookup shows a timeout, that suggests the request is reaching a bad or unreachable name server.

  1. Check whether IPv6 is part of the failure.

If nslookup behavior points to IPv6 trouble, that is a useful clue, not a final diagnosis. One report suggested temporarily unchecking IPv6 in the adapter settings as a test, then turning it back on to compare behavior. Use that only as a diagnostic step if you can restore it afterward.

  1. Look at Windows status screens and logs for the pattern.

The network status page, adapter status, and Event Viewer can show whether Windows thinks the adapter disconnected, renegotiated, or lost its network settings during sleep. I would check the adapter status first, then the System log in Event Viewer for anything tied to the network adapter or DHCP around the wake time. The exact wording varies by Windows version and driver, so use the screen to match the failure mode rather than hunting for one fixed error string.

If you see that the adapter comes back only after you toggle it, the problem is probably driver or power management. If the adapter is fine but the DNS server in ipconfig /all changes only after a renew, the router or DHCP server is the better suspect.

When it keeps happening

A repeat failure after every sleep cycle usually points to a driver, firmware, VPN, or security suite conflict rather than a one-off cache problem. If flushing DNS helps once but the problem returns after the next sleep, the cache was not the root cause.

At that point, update the network adapter driver from the PC or motherboard maker, not just from a generic driver search. If the issue started after a driver update, roll back to the last known good one instead of trying random changes. Also check router firmware and router DNS settings if more than one device shows odd lookups after renewal.

A useful test is to sleep the PC, wake it, and run the same nslookup and ipconfig /all checks before and after each change. If the DNS server in ipconfig changes from bad to correct after a renewal, that points to a lease or router issue. If the adapter itself stops responding until you toggle it, the fault is lower in the stack, usually the driver or power management.

Conclusion

If it happens again, compare the wake-up state before and after a reconnect, a renew, and a DNS flush. That will tell you whether to fix the adapter, the lease, the VPN, or the router next.

Frequently Asked Questions

Should I flush DNS or renew the lease first?

Flush DNS first only if the adapter is already working and the problem looks like stale name resolution. If that does not help, renew the lease next, because `ipconfig /renew` can pull fresh network and DNS data after wake.

How do I know it is not just my internet going down?

If a site works by IP address but not by name, the internet link is probably still up and DNS is the failure. If both the name and the IP fail, the problem is broader than DNS and usually sits with the adapter, router, or connection.

Why does it work again after a reboot?

A reboot resets the adapter, DHCP state, and DNS cache all at once, so it can hide the real cause. That is why it is better to test after sleep with `nslookup` and `ipconfig` before you reboot anything.

Sources