DNS not resolving in Windows 11: prove name resolution before changing DNS settings
Use IP configuration, nslookup and a browser comparison to separate DNS failure from general connectivity or one-site failure.
- Check whether the PC has a normal IP address and default gateway with ipconfig /all.
- Try the same site in another browser and verify the hostname is typed correctly.
- Run nslookup for a known hostname and record the DNS server/result.
- Do not change DNS servers yet if the whole connection is down or the adapter has a 169.254.x.x address.
What this problem usually means
DNS translates host names into addresses. Microsoft documents nslookup specifically for diagnosing DNS infrastructure, while the Windows connectivity guidance recommends checking IP configuration and flushing the resolver cache when name resolution is a plausible branch.
Work from the narrowest fix to the broader one.
Flush the local resolver cache
Low riskWhy this belongs here: A stale local DNS cache can preserve an outdated answer even when the network itself is working.
- Open Command Prompt or Terminal.
- Run ipconfig /flushdns.
- Retry the hostname and compare the result.
ipconfig /flushdnsCompare the configured DNS path with nslookup
Low riskWhy this belongs here: nslookup can show whether the configured resolver answers the query, which is more informative than randomly replacing DNS settings.
- Run nslookup example.com using the default resolver.
- Record whether the query resolves, times out or returns a name error.
- If you manage the network, compare against a known working resolver only as a diagnostic test.
Check proxy/VPN and router DNS only when the evidence points there
Low riskWhy this belongs here: VPN, proxy and router DNS settings can affect name resolution, but they should not be disabled blindly when only one website is unavailable.
- Temporarily disconnect a VPN only when the failure appears only while it is active.
- Review Windows proxy settings for unexpected manual configuration.
- If every device on the same network has DNS trouble, troubleshoot the router/provider DNS path.
When this guide stops being the right path
If only one hostname fails while other sites resolve normally, do not reset the Windows network stack; the domain, DNS record or destination service may be the problem.
If the problem is still not fixed
If DNS resolves correctly but the browser reports reset, refused or timeout errors, continue with the matching browser/network error record.
Sources reviewed for this page
Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.