Introduction
The "DNS server not responding" error on Windows 11 is one of the most misleading network failures. Your Wi-Fi or Ethernet adapter still says Connected, the signal bars are full, and local devices such as printers may still respond, yet no website will load. Chrome may show DNS_PROBE_FINISHED_NXDOMAIN, Edge may say "Hmm, we can't reach this page", and ping google.com may fail while ping 8.8.8.8 succeeds.
DNS is the part of the network stack that turns a name such as example.com into an IP address. When the configured DNS server stops answering, the name never becomes an address, so the browser has nothing to connect to. The physical link can be perfectly healthy while name resolution is completely broken.
This guide walks through the same order an IT support technician would use: confirm that the problem is DNS, identify which DNS server is failing, then apply the least disruptive fix first. It includes copy-ready PowerShell and Command Prompt commands, expected output, before-and-after examples, Windows Event IDs, compatibility notes, and links to free diagnostic tools.
Problem Description
A Windows 11 PC resolves most names in milliseconds. The DNS Client service (Dnscache) checks the local cache, then sends a query to the DNS servers configured on the active network adapter. Those servers are usually supplied by DHCP from the router, but they can also be set manually or pushed by a VPN.
When the DNS server does not respond, Windows retries the query with increasing delays (roughly 1, 2, 4 and 8 seconds), so a failure can take several seconds to appear. With two servers configured, Windows also queries the second server when the first does not answer. That is why some failures feel instant while others hang before the browser shows an error.
The important distinction is this: the adapter is connected, but name resolution is failing. You may still be able to open the router's admin page by IP address, print to a local printer, or ping 8.8.8.8. Those tests prove the link is alive. They do not prove DNS is working.
Symptoms
- "DNS server not responding" appears in Windows Network Diagnostics.
- Chrome shows
DNS_PROBE_FINISHED_NXDOMAINorDNS_PROBE_FINISHED_NO_INTERNET. - Edge shows "Hmm, we can't reach this page" with a DNS error.
- Firefox shows "Server Not Found".
ping google.comfails with "Ping request could not find host", butping 8.8.8.8succeeds.nslookup google.comreturns "DNS request timed out" or "Server failed".- The internet works on a phone or another PC on the same network.
- The problem starts after a Windows Update, waking from sleep, connecting to a VPN, or joining a different Wi-Fi network.
- Some sites load and others do not, which usually points to cache, hosts-file, or filtering problems rather than a total DNS outage.
Root Causes
| Root cause | Typical clue | First check |
|---|---|---|
| Stale or corrupted DNS cache | Some sites fail, others work; problem starts after sleep or VPN use | Clear-DnsClientCache |
| ISP or router DNS outage | Every device on the network fails, including phones | Test with nslookup google.com 1.1.1.1 |
| Router DNS relay failure | Router admin page opens by IP, but names fail | Reboot the router; set DNS on the PC |
| Winsock or TCP/IP corruption | Failure after a VPN or security-suite update | netsh winsock reset |
| IPv6 DNS misconfiguration | A delay, then failure; IPv6 is enabled | Get-DnsClientServerAddress -AddressFamily IPv6 |
| Security software or DNS filtering | Browser fails while some command-line lookups work | Temporarily disable web protection |
| VPN or NRPT leftovers | Fails only on a corporate network or after VPN disconnect | Get-DnsClientNrptPolicy |
| Adapter power management | Fails after waking from sleep | Device Manager power setting |
| Outdated or rolled-back adapter driver | Starts after a Windows Update | Update or roll back the driver |
| DNS Client service stopped | Event ID 8001; service is not running | Get-Service Dnscache |
| DNS over HTTPS (DoH) unreachable | Fails when encryption is set to "Encrypted only" | Get-DnsClientDohServerAddress |
| Hosts-file entry or malware | One domain fails while others work | Read the hosts file |
Before You Start
Open Terminal (Admin) or PowerShell (Admin). Most diagnostic commands work without elevation, but reset commands and service changes require it.
- Right-click Start and choose Terminal (Admin).
- Confirm the window title says Administrator.
- Run
Get-NetAdapterand note the exact Name of the active adapter. The examples below useWi-Fi; replace it withEthernetor your adapter's name if needed. - If you are on a managed or corporate device, check with IT before changing DNS or running a network reset. Group Policy may reapply the original settings.
Get-NetAdapter | Format-Table Name, InterfaceDescription, Status, LinkSpeed -AutoSizeExpected output (names and speeds vary):
Name InterfaceDescription Status LinkSpeed
---- -------------------- ------ ---------
Wi-Fi Intel(R) Wi-Fi 6 AX201 160MHz Up 866.7 Mbps
Ethernet Realtek PCIe GbE Family Controller Disconnected 0 bpsStep 1: Confirm the Failure Is DNS
Do not change anything until you know which layer is failing. Run these three checks in order.
Get-NetIPConfiguration
Get-DnsClientServerAddress -AddressFamily IPv4
Resolve-DnsName example.com -Type AA failing lookup looks like this:
Resolve-DnsName : example.com : This operation returned because the timeout period expired
+ CategoryInfo : OperationTimeout: (example.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : ERROR_TIMEOUT,Microsoft.DnsClient.Commands.ResolveDnsNameA working lookup returns a record:
Name Type TTL Section IPAddress
---- ---- --- ------- ---------
example.com A 60 Answer 93.184.216.34IP addresses change over time, so treat the address itself as an example. The important part is that an answer arrives.
Next, test a public resolver directly. This separates "the PC cannot do DNS at all" from "the configured DNS server is the problem".
Resolve-DnsName example.com -Server 1.1.1.1 -Type A
nslookup example.com 1.1.1.1
Test-NetConnection 8.8.8.8 -InformationLevel Detailed
Test-NetConnection 1.1.1.1 -Port 53| Result | What it means | Go to |
|---|---|---|
Default lookup fails, -Server 1.1.1.1 works | The configured DNS server is failing | Fix 1 and Fix 2 |
Both lookups fail, but ping 8.8.8.8 works | Outbound DNS is blocked or the stack is damaged | Fix 5 and Fix 9 |
ping 8.8.8.8 also fails | The network path is down | Fix 3, Fix 4, Fix 11 |
| Only one domain fails | Cache, hosts file, or filtering | Fix 1 and the hosts-file check |
| Fails after a VPN disconnect | VPN or NRPT leftovers | Fix 7 |
| Fails only when DoH is enabled | DNS over HTTPS problem | Fix 8 |
Fix 1: Flush the DNS Cache and Restart the DNS Client
A stale cache is the most common cause of partial DNS failures. Flushing it is safe and takes a second.
Clear-DnsClientCache
ipconfig /flushdns
ipconfig /registerdnsClear-DnsClientCache and ipconfig /flushdns do the same job; running both is harmless. ipconfig /registerdns asks Windows to re-register this PC's name with DNS, which matters mainly on domain networks.
Now confirm the DNS Client service is running:
Get-Service -Name DnscacheBefore (service stopped):
Status Name DisplayName
------ ---- -----------
Stopped Dnscache DNS ClientIf it is stopped or set to Disabled, repair it:
Set-Service -Name Dnscache -StartupType Automatic
Start-Service Dnscache
Get-Service -Name DnscacheAfter:
Status Name DisplayName
------ ---- -----------
Running Dnscache DNS ClientTest again with Resolve-DnsName example.com -Type A. If names resolve, stop here. If they do not, continue.
Fix 2: Switch to a Reliable Public DNS Server
If the router or ISP resolver is down, changing the PC's DNS servers bypasses it. This is the highest-value fix in most home and small-office cases.
Check the current setting first:
Get-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -AddressFamily IPv4Before (router-only DNS):
InterfaceAlias InterfaceIndex ServerAddresses
-------------- ------------ ---------------
Wi-Fi 12 {192.168.1.1}Apply Cloudflare DNS:
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("1.1.1.1","1.0.0.1")
Clear-DnsClientCache
Get-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -AddressFamily IPv4After:
InterfaceAlias InterfaceIndex ServerAddresses
-------------- ------------ ---------------
Wi-Fi 12 {1.1.1.1, 1.0.0.1}Verify that resolution now works:
Resolve-DnsName example.com -Type A
nslookup example.comTo return to automatic DHCP settings later:
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses
Clear-DnsClientCache| Provider | Primary | Secondary | Best for |
|---|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 | Speed and privacy |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | Broad reliability |
| Quad9 | 9.9.9.9 | 149.112.112.112 | Malware-domain blocking |
| OpenDNS | 208.67.222.222 | 208.67.220.220 | Content filtering options |
Fix 3: Restart the Router and Modem
A router can keep its Wi-Fi signal while its DNS relay has stopped working. Restarting clears that state.
- Unplug the router and the modem.
- Wait at least 60 seconds.
- Plug the modem back in first and wait for its status lights to stabilise.
- Plug the router back in and wait for the internet light.
- Reconnect the PC and test with
Resolve-DnsName example.com -Type A.
If a phone or another PC on the same network also fails, the problem is almost certainly the router, the ISP, or the internet connection, not this Windows 11 PC.
Fix 4: Forget and Reconnect the Wi-Fi Network
A saved Wi-Fi profile can keep an old DNS setting or a stale security state. Removing the profile forces Windows to rebuild it.
- Open Settings > Network & internet > Wi-Fi > Manage known networks.
- Select the network and choose Forget.
- Reconnect and enter the Wi-Fi password.
- Run
Clear-DnsClientCacheand test again.
You can also list and remove profiles from an admin terminal:
netsh wlan show profiles
netsh wlan delete profile name="YourNetworkName"Replace YourNetworkName with the exact profile name shown by the first command.
Fix 5: Reset Winsock and the TCP/IP Stack
If DNS broke after a VPN, proxy, or security-suite update, the Winsock catalogue or TCP/IP stack may be corrupted. This reset rebuilds both.
ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh winsock reset
netsh int ip resetRestart Windows after the last command. The reset takes effect at boot.
Before (lookup timing out):
Resolve-DnsName : example.com : This operation returned because the timeout period expiredAfter the restart:
Name Type TTL Section IPAddress
---- ---- --- ------- ---------
example.com A 60 Answer 93.184.216.34Fix 6: Check IPv6 DNS Settings
Windows may try IPv6 DNS first. If the IPv6 DNS server is unreachable, the lookup can stall before IPv4 is used.
Get-DnsClientServerAddress -AddressFamily IPv6
Get-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6If IPv6 is enabled but the listed DNS server is not reachable on your network, the best fix is to correct the IPv6 DNS setting or let DHCP supply it. Disabling IPv6 is a workaround, not a repair.
Disable-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6
Clear-DnsClientCacheRe-enable it when you are finished testing:
Enable-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6Fix 7: Remove VPN and NRPT Interference
VPN clients often add a Name Resolution Policy Table (NRPT) rule that sends specific domains to a private DNS server. If the VPN disconnects without removing the rule, lookups for those domains can fail.
Get-VpnConnection
Get-DnsClientNrptPolicyIf a rule belongs to a VPN you no longer use, remove it. Replace the example name with the exact rule name returned by Get-DnsClientNrptPolicy.
Remove-DnsClientNrptRule -Name "ExampleVpnRule"
Clear-DnsClientCacheAlso disconnect the VPN, then disable or uninstall unused virtual adapters such as TAP-Windows or Wintun in Device Manager. Restart and test again.
Fix 8: Test DNS over HTTPS (DoH)
Windows 11 can encrypt DNS queries with DoH. If the chosen DoH template is unreachable, name resolution fails even though ordinary DNS would work.
Get-DnsClientDohServerAddress
Get-DnsClientGlobalSettingIn the Settings app, open Network & internet > Wi-Fi (or Ethernet) > your network > DNS server assignment > Edit. Set DNS over HTTPS to Off (older Windows 11 builds label this Unencrypted only) and test.
If DNS works without encryption, the DoH server or the path to it is the problem. Re-enable encryption only after confirming that the provider's DoH template is reachable from this network.
Fix 9: Check Firewall and Antivirus DNS Filtering
Security suites with web protection, parental controls, or DNS filtering can intercept or block port 53. This often produces a browser failure while some command-line tools still work.
- Temporarily disable the third-party suite's web or DNS protection. Do not disable the whole product for longer than the test.
- Run
Resolve-DnsName example.com -Type Aagain. - If DNS recovers, add an exception for the DNS servers or disable the DNS-filtering feature permanently.
Check the Windows firewall profiles:
Get-NetFirewallProfile | Format-Table Name, EnabledWindows Defender Firewall rarely blocks outbound DNS by default. Third-party suites and endpoint-protection agents are the more common cause.
Fix 10: Stop Windows From Powering Down the Adapter
Power management can leave the adapter or DNS Client in a bad state after sleep. This matches the pattern "DNS fails every time I wake the laptop".
Check the current setting first. AllowComputerToTurnOffDevice is a property of the power-management object, not a parameter of the cmdlet, so read it with Format-List:
Get-NetAdapterPowerManagement -Name "Wi-Fi" | Format-List Name, AllowComputerToTurnOffDeviceBefore:
Name : Wi-Fi
AllowComputerToTurnOffDevice : EnabledChange the property, then pipe the object back to Set-NetAdapterPowerManagement:
$power = Get-NetAdapter -Name "Wi-Fi" | Get-NetAdapterPowerManagement
$power.AllowComputerToTurnOffDevice = 'Disabled'
$power | Set-NetAdapterPowerManagementAfter:
Name : Wi-Fi
AllowComputerToTurnOffDevice : DisabledYou can also do this in Device Manager > Network adapters > your adapter > Properties > Power Management by clearing Allow the computer to turn off this device to save power.
If the problem started after a Windows Update, open Device Manager, right-click the adapter, and choose Update driver or Roll back driver if the rollback option is available.
Fix 11: Reset All Network Settings
A full network reset removes and reinstalls network adapters and restores networking components to their defaults. It is the broadest software-level fix and the last one to try before hardware or ISP support.
- Open Settings > Network & internet > Advanced network settings > Network reset.
- Choose Reset now and confirm.
- Wait for the restart.
- Reconnect to Wi-Fi and test with
Resolve-DnsName example.com -Type A.
Fix 12: Check the Router's DNS Configuration
If every device on the network fails, fix DNS at the router instead of on each PC.
- Open the router admin page. Common addresses are
192.168.1.1,192.168.0.1, or10.0.0.1. The default gateway fromGet-NetIPConfigurationis the correct address. - Find the WAN or Internet DNS settings and set primary
1.1.1.1, secondary1.0.0.1, or use the DNS servers supplied by your ISP. - Find the DHCP DNS settings and make sure the router is not handing out a dead DNS server.
- Save the settings and reboot the router.
- Reconnect the PC, run
Clear-DnsClientCache, and test.
If the router hands out its own LAN IP as the DNS server, the router's DNS relay must be working. A failed relay explains why the PC can open the router page by IP but cannot resolve names.
Event Viewer Evidence: What Event ID 1014 Tells You
Windows logs DNS Client failures in the System log. Event ID 1014 is the classic "none of the configured DNS servers responded" warning.
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-DNS-Client'; Id=1014} -MaxEvents 10 |
Format-List TimeCreated, Id, LevelDisplayName, MessageThe DNS Client Operational log is disabled by default. Enable it when you need query-level detail:
wevtutil sl Microsoft-Windows-DNS-Client/Operational /e:true
Get-WinEvent -LogName 'Microsoft-Windows-DNS-Client/Operational' -MaxEvents 20 |
Format-Table TimeCreated, Id, LevelDisplayName -AutoSize| Event ID | Log | Meaning | What to do |
|---|---|---|---|
| 1014 | System | Name resolution timed out after none of the configured DNS servers responded | The main evidence for this error. Confirm server reachability and flush the cache |
| 1013 | DNS Client Operational | Same all-server timeout message, logged in the Operational log | Enable the Operational log and correlate the query name with the failure |
| 1015 | DNS Client Operational | Query timed out after a specific DNS server failed to respond | Identifies which server address is failing |
| 1000 | DNS Client Operational | No IPv4 DNS servers are configured on any interface | Check DHCP and static DNS settings |
| 1019 | DNS Client Operational | No IPv6 DNS servers are configured on any interface | Usually harmless; investigate only if IPv6 is required |
| 1011 | DNS Client Operational | Error reading the local hosts file | Check the hosts file's content and permissions |
| 1023 | System | The Name Resolution Policy Table (NRPT) is corrupted | Review VPN and DirectAccess NRPT rules |
| 8001 | System | "Unable to start DNS Client service" | Check the service startup type, dependencies and Event ID 7000/7001 |
You can also inspect the hosts file directly. A malicious or accidental entry can break a single domain while everything else works.
Get-Content C:\Windows\System32\drivers\etc\hostsWindows Version Compatibility
| Windows version | Support | Notes |
|---|---|---|
| Windows 11 24H2 | Supported | Settings paths and PowerShell cmdlets match this guide |
| Windows 11 23H2 | Supported | Settings paths match this guide |
| Windows 11 22H2 | Supported | Settings paths match this guide |
| Windows 11 21H2 | Supported | Some Settings pages may use slightly older labels |
| Windows 10 22H2 | Supported | Use Control Panel > Network Connections for adapter properties if the Settings path differs |
| Windows 10 21H2 / LTSC | Mostly supported | DoH options may be missing; all DNS cmdlets still apply |
Before and After: What a Fixed Configuration Looks Like
Use this table as a quick sanity check after the fixes.
| Check | Before (broken) | After (fixed) |
|---|---|---|
Get-DnsClientServerAddress | {192.168.1.1} and that server does not answer | {1.1.1.1, 1.0.0.1} |
Resolve-DnsName example.com -Type A | Timeout or "server failure" | Returns an A record |
nslookup example.com | "DNS request timed out" | "Non-authoritative answer" with an address |
Get-Service Dnscache | Stopped | Running |
| Browser | DNS_PROBE_FINISHED_NXDOMAIN | Page loads normally |
| Event Viewer | Repeated Event ID 1014 | No new 1014 events after the fix |
Frequently Asked Questions
What does "DNS server not responding" actually mean?
Windows sent a DNS query to the configured server and received no usable answer before the timeout expired. The network link can still be connected; the failure is in name resolution, not in the Wi-Fi signal.
Is this the same as having no internet?
No. You can have a working internet connection and still fail DNS. Test with ping 8.8.8.8. If that succeeds but ping google.com fails, the problem is DNS-specific.
Why does DNS work on my phone but not on my Windows 11 PC?
The phone may be using a different DNS server, a different Wi-Fi band, or a private DNS setting. The fault is likely in the PC's adapter configuration, DNS cache, VPN software, or network stack.
Does changing DNS to 1.1.1.1 make my internet faster?
It can make browsing feel faster when the old resolver was slow, but it does not increase your download bandwidth. DNS only affects name lookup time.
Which DNS provider should I use?
Cloudflare (1.1.1.1) is a good default for speed and privacy. Google (8.8.8.8) is widely reliable. Quad9 (9.9.9.9) blocks known malicious domains. Use your ISP or company DNS if you need internal names.
Why does the error come back after waking from sleep?
Power management can turn off the adapter or leave the DNS Client in a bad state. Disable "Allow the computer to turn off this device to save power" for the adapter and confirm the Dnscache service is set to Automatic.
Can malware cause this error?
Yes. Malware can change DNS settings or add entries to the hosts file. Run a full scan and check C:\Windows\System32\drivers\etc\hosts if only specific sites fail.
Will a system restore fix it?
It can, if the problem started immediately after a driver, VPN, or security-software installation. Try the less disruptive fixes first.
Why do only some websites fail?
That pattern usually points to a stale cache entry, a hosts-file entry, DNS filtering, or a resolver that is dropping specific queries. Flush the cache and test the same name against 1.1.1.1.
Can my ISP block third-party DNS servers?
Some networks redirect or block port 53 to force their own resolver. If Resolve-DnsName example.com -Server 1.1.1.1 fails but ordinary browsing works, test DNS over HTTPS or ask the ISP.
How do I undo all the DNS changes?
Run Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses, then Clear-DnsClientCache. This returns the adapter to DHCP-supplied DNS servers.
Do I need to restart after flushing the DNS cache?
No. A cache flush takes effect immediately. Restart only after netsh winsock reset, netsh int ip reset, or a network reset.
Related Guides and Tools
Use these free tools to confirm the diagnosis and fix related problems:
- DNS Cache Flusher and Network Reset Guide — generate the exact flush and reset commands for Windows.
- Network Troubleshooter Guide — work through adapter, gateway, and connectivity checks.
- Event Viewer Log Analyzer — interpret DNS Client events and other Windows log entries.
- Windows Error Code Lookup — decode a
0xerror code or stop code. - Fix Network Printer Not Connecting on Windows 11 — printer discovery also depends on name resolution.
- Fix Windows 11 Update Error 0x800f0982 — update failures often appear alongside network errors.
- Outlook Not Opening on Windows 11 — Outlook connection problems can look like DNS failures.
- IT Troubleshooting Center — browse all Windows and networking guides.
Conclusion
Start by proving the failure is DNS, not the physical link: Resolve-DnsName against the default server and against 1.1.1.1 tells you which side is broken. In most cases, flushing the cache and switching to a working resolver fixes the problem within a few minutes. If the error returns after sleep, a VPN disconnect, or a security-software update, work through the stack reset, IPv6, NRPT, DoH, and power-management checks in that order.
If every device on the network fails, stop changing the PC and investigate the router, the ISP, or the DHCP-supplied DNS settings. If only this PC fails and all twelve fixes have been tried, check Event Viewer for Event ID 1014 and review the exact query names and server addresses in the DNS Client Operational log before escalating to hardware support.