Fix DNS Server Not Responding Error in Windows 11 (2026 Guide)

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.

Windows DNS resolution flow from browser to recursive resolver
Figure 1 — How Windows resolves a name, and where the 'DNS server not responding' failure occurs. Steps 1 and 2 are local to the PC; steps 3 and 4 depend on the DNS server and the network path to it.

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_NXDOMAIN or DNS_PROBE_FINISHED_NO_INTERNET.
  • Edge shows "Hmm, we can't reach this page" with a DNS error.
  • Firefox shows "Server Not Found".
  • ping google.com fails with "Ping request could not find host", but ping 8.8.8.8 succeeds.
  • nslookup google.com returns "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 causeTypical clueFirst check
Stale or corrupted DNS cacheSome sites fail, others work; problem starts after sleep or VPN useClear-DnsClientCache
ISP or router DNS outageEvery device on the network fails, including phonesTest with nslookup google.com 1.1.1.1
Router DNS relay failureRouter admin page opens by IP, but names failReboot the router; set DNS on the PC
Winsock or TCP/IP corruptionFailure after a VPN or security-suite updatenetsh winsock reset
IPv6 DNS misconfigurationA delay, then failure; IPv6 is enabledGet-DnsClientServerAddress -AddressFamily IPv6
Security software or DNS filteringBrowser fails while some command-line lookups workTemporarily disable web protection
VPN or NRPT leftoversFails only on a corporate network or after VPN disconnectGet-DnsClientNrptPolicy
Adapter power managementFails after waking from sleepDevice Manager power setting
Outdated or rolled-back adapter driverStarts after a Windows UpdateUpdate or roll back the driver
DNS Client service stoppedEvent ID 8001; service is not runningGet-Service Dnscache
DNS over HTTPS (DoH) unreachableFails when encryption is set to "Encrypted only"Get-DnsClientDohServerAddress
Hosts-file entry or malwareOne domain fails while others workRead 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.

  1. Right-click Start and choose Terminal (Admin).
  2. Confirm the window title says Administrator.
  3. Run Get-NetAdapter and note the exact Name of the active adapter. The examples below use Wi-Fi; replace it with Ethernet or your adapter's name if needed.
  4. 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.
PowerShell
Get-NetAdapter | Format-Table Name, InterfaceDescription, Status, LinkSpeed -AutoSize

Expected output (names and speeds vary):

Output
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 bps

Step 1: Confirm the Failure Is DNS

Do not change anything until you know which layer is failing. Run these three checks in order.

PowerShell
Get-NetIPConfiguration
Get-DnsClientServerAddress -AddressFamily IPv4
Resolve-DnsName example.com -Type A

A failing lookup looks like this:

Output
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.ResolveDnsName

A working lookup returns a record:

Output
Name         Type TTL Section IPAddress
----         ---- --- ------- ---------
example.com  A    60  Answer  93.184.216.34

IP 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".

PowerShell
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
ResultWhat it meansGo to
Default lookup fails, -Server 1.1.1.1 worksThe configured DNS server is failingFix 1 and Fix 2
Both lookups fail, but ping 8.8.8.8 worksOutbound DNS is blocked or the stack is damagedFix 5 and Fix 9
ping 8.8.8.8 also failsThe network path is downFix 3, Fix 4, Fix 11
Only one domain failsCache, hosts file, or filteringFix 1 and the hosts-file check
Fails after a VPN disconnectVPN or NRPT leftoversFix 7
Fails only when DoH is enabledDNS over HTTPS problemFix 8
DNS troubleshooting decision tree for Windows 11
Figure 2 — Use this decision tree after Step 1. Work from the top down and stop at the first branch that matches your result.

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.

PowerShell
Clear-DnsClientCache
ipconfig /flushdns
ipconfig /registerdns

Clear-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:

PowerShell
Get-Service -Name Dnscache

Before (service stopped):

Output
Status   Name      DisplayName
------   ----      -----------
Stopped  Dnscache  DNS Client

If it is stopped or set to Disabled, repair it:

PowerShell
Set-Service -Name Dnscache -StartupType Automatic
Start-Service Dnscache
Get-Service -Name Dnscache

After:

Output
Status   Name      DisplayName
------   ----      -----------
Running  Dnscache  DNS Client

Test 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:

PowerShell
Get-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -AddressFamily IPv4

Before (router-only DNS):

Output
InterfaceAlias InterfaceIndex ServerAddresses
-------------- ------------ ---------------
Wi-Fi          12           {192.168.1.1}

Apply Cloudflare DNS:

PowerShell
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("1.1.1.1","1.0.0.1")
Clear-DnsClientCache
Get-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -AddressFamily IPv4

After:

Output
InterfaceAlias InterfaceIndex ServerAddresses
-------------- ------------ ---------------
Wi-Fi          12           {1.1.1.1, 1.0.0.1}

Verify that resolution now works:

PowerShell
Resolve-DnsName example.com -Type A
nslookup example.com

To return to automatic DHCP settings later:

PowerShell
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses
Clear-DnsClientCache
ProviderPrimarySecondaryBest for
Cloudflare1.1.1.11.0.0.1Speed and privacy
Google Public DNS8.8.8.88.8.4.4Broad reliability
Quad99.9.9.9149.112.112.112Malware-domain blocking
OpenDNS208.67.222.222208.67.220.220Content 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.

  1. Unplug the router and the modem.
  2. Wait at least 60 seconds.
  3. Plug the modem back in first and wait for its status lights to stabilise.
  4. Plug the router back in and wait for the internet light.
  5. 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.

  1. Open Settings > Network & internet > Wi-Fi > Manage known networks.
  2. Select the network and choose Forget.
  3. Reconnect and enter the Wi-Fi password.
  4. Run Clear-DnsClientCache and test again.

You can also list and remove profiles from an admin terminal:

PowerShell
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.

PowerShell
ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Restart Windows after the last command. The reset takes effect at boot.

Before (lookup timing out):

Output
Resolve-DnsName : example.com : This operation returned because the timeout period expired

After the restart:

Output
Name         Type TTL Section IPAddress
----         ---- --- ------- ---------
example.com  A    60  Answer  93.184.216.34

Fix 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.

PowerShell
Get-DnsClientServerAddress -AddressFamily IPv6
Get-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6

If 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.

PowerShell
Disable-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6
Clear-DnsClientCache

Re-enable it when you are finished testing:

PowerShell
Enable-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6

Fix 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.

PowerShell
Get-VpnConnection
Get-DnsClientNrptPolicy

If 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.

PowerShell
Remove-DnsClientNrptRule -Name "ExampleVpnRule"
Clear-DnsClientCache

Also 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.

PowerShell
Get-DnsClientDohServerAddress
Get-DnsClientGlobalSetting

In 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.

  1. Temporarily disable the third-party suite's web or DNS protection. Do not disable the whole product for longer than the test.
  2. Run Resolve-DnsName example.com -Type A again.
  3. If DNS recovers, add an exception for the DNS servers or disable the DNS-filtering feature permanently.

Check the Windows firewall profiles:

PowerShell
Get-NetFirewallProfile | Format-Table Name, Enabled

Windows 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:

PowerShell
Get-NetAdapterPowerManagement -Name "Wi-Fi" | Format-List Name, AllowComputerToTurnOffDevice

Before:

Output
Name                         : Wi-Fi
AllowComputerToTurnOffDevice : Enabled

Change the property, then pipe the object back to Set-NetAdapterPowerManagement:

PowerShell
$power = Get-NetAdapter -Name "Wi-Fi" | Get-NetAdapterPowerManagement
$power.AllowComputerToTurnOffDevice = 'Disabled'
$power | Set-NetAdapterPowerManagement

After:

Output
Name                         : Wi-Fi
AllowComputerToTurnOffDevice : Disabled

You 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.

  1. Open Settings > Network & internet > Advanced network settings > Network reset.
  2. Choose Reset now and confirm.
  3. Wait for the restart.
  4. 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.

  1. Open the router admin page. Common addresses are 192.168.1.1, 192.168.0.1, or 10.0.0.1. The default gateway from Get-NetIPConfiguration is the correct address.
  2. Find the WAN or Internet DNS settings and set primary 1.1.1.1, secondary 1.0.0.1, or use the DNS servers supplied by your ISP.
  3. Find the DHCP DNS settings and make sure the router is not handing out a dead DNS server.
  4. Save the settings and reboot the router.
  5. 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.

PowerShell
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-DNS-Client'; Id=1014} -MaxEvents 10 |
  Format-List TimeCreated, Id, LevelDisplayName, Message

The DNS Client Operational log is disabled by default. Enable it when you need query-level detail:

PowerShell
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 IDLogMeaningWhat to do
1014SystemName resolution timed out after none of the configured DNS servers respondedThe main evidence for this error. Confirm server reachability and flush the cache
1013DNS Client OperationalSame all-server timeout message, logged in the Operational logEnable the Operational log and correlate the query name with the failure
1015DNS Client OperationalQuery timed out after a specific DNS server failed to respondIdentifies which server address is failing
1000DNS Client OperationalNo IPv4 DNS servers are configured on any interfaceCheck DHCP and static DNS settings
1019DNS Client OperationalNo IPv6 DNS servers are configured on any interfaceUsually harmless; investigate only if IPv6 is required
1011DNS Client OperationalError reading the local hosts fileCheck the hosts file's content and permissions
1023SystemThe Name Resolution Policy Table (NRPT) is corruptedReview VPN and DirectAccess NRPT rules
8001System"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.

PowerShell
Get-Content C:\Windows\System32\drivers\etc\hosts

Windows Version Compatibility

Windows versionSupportNotes
Windows 11 24H2SupportedSettings paths and PowerShell cmdlets match this guide
Windows 11 23H2SupportedSettings paths match this guide
Windows 11 22H2SupportedSettings paths match this guide
Windows 11 21H2SupportedSome Settings pages may use slightly older labels
Windows 10 22H2SupportedUse Control Panel > Network Connections for adapter properties if the Settings path differs
Windows 10 21H2 / LTSCMostly supportedDoH 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.

CheckBefore (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 ATimeout or "server failure"Returns an A record
nslookup example.com"DNS request timed out""Non-authoritative answer" with an address
Get-Service DnscacheStoppedRunning
BrowserDNS_PROBE_FINISHED_NXDOMAINPage loads normally
Event ViewerRepeated Event ID 1014No 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.

Use these free tools to confirm the diagnosis and fix related problems:

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.

We Value Your Privacy

We use cookies to improve your browsing experience, analyze traffic, and display relevant advertisements.