How Do I Fix DNS Server Not Responding on Windows 11?

The "DNS server not responding" error on Windows 11 means your PC sent a DNS query and received no reply. The fastest fix is to open Settings → Network & Internet → your connection → DNS server assignment, switch from Automatic to Manual, and enter 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) as the preferred DNS, then run ipconfig /flushdns in an elevated Command Prompt. If the error clears, your ISP's resolver was the problem. If it persists, work through the root causes below in order.

What This Error Actually Means

Windows 11's Network Troubleshooter labels the problem "DNS server not responding" when it sends a test query and receives no answer within the timeout window. The error is a symptom, not a cause — the real culprit could be anywhere from a misconfigured Windows service to a failing router to an ISP outage. Before troubleshooting, open Command Prompt and run ping 8.8.8.8. If replies come back, your internet connection is intact and only DNS is broken. If ping also fails, you have a broader connectivity issue and should start at your router or modem, not your DNS settings.

Root Causes, Ranked by How Often They Occur

1. ISP DNS server is slow, down, or filtering queries — the most common cause by far. ISP resolvers are less reliable than public alternatives and can be throttled or silently filtered on certain network types. Switching to a public DNS rules this out in under 60 seconds.
2. Windows DNS Client service has stopped or is stuck — the dnscache service caches and forwards all DNS queries. It stalls occasionally after Windows Update restarts, after security software changes, or after unexpected shutdowns.
3. Corrupted TCP/IP stack or Winsock catalog — happens after incomplete updates, aggressive network optimization tools, or malware removal. The stack silently drops or rejects packets.
4. IPv6 misconfiguration causing query stalls — Windows 11 queries IPv6 DNS first by default. If your router advertises an IPv6 prefix but has no working IPv6 DNS upstream, every lookup stalls waiting for the IPv6 timeout before the IPv4 fallback runs. On some configurations the fallback never triggers and queries fail outright.
5. Outdated or corrupted network adapter driver — especially common on machines that upgraded from Windows 10 without refreshing drivers, and on Intel Wi-Fi 6 and Realtek Ethernet adapters.
6. Router firmware bug or stuck DNS relay — some firmware versions stop forwarding DNS queries while continuing to hand out the router's own LAN IP as the DNS server address. Clients see a valid DNS address but get no answers from it.
7. Third-party VPN, firewall, or antivirus DNS hook — software that intercepts DNS queries can break resolution entirely if it crashes, enters an error state, or conflicts with Windows 11's native DNS-over-HTTPS stack.
8. Firewall rule blocking UDP or TCP port 53 — can be introduced by an imported group policy, a VPN kill switch left active after disconnect, or an overly aggressive security script.

Fix 1: Switch to a Public DNS Server

This is the highest-yield first step because it bypasses both your ISP's resolver and your router's DNS relay at the same time.

1. Open Settings → Network & Internet.
2. Click Wi-Fi or Ethernet, then click your specific connection name.
3. Scroll to DNS server assignment and click Edit.
4. Change the dropdown from Automatic (DHCP) to Manual.
5. Enable the IPv4 toggle and set:
   • Preferred DNS: 8.8.8.8
   • Alternate DNS: 8.8.4.4
6. Enable the IPv6 toggle and set:
   • Preferred DNS: 2001:4860:4860::8888
   • Alternate DNS: 2001:4860:4860::8844
7. Click Save.

Then open an elevated Command Prompt (right-click Start → Terminal (Admin)) and run:

If nslookup returns IP addresses under the answer section, DNS is working. If websites still fail after DNS resolves successfully, the problem is no longer DNS — check your browser proxy settings or try a different browser to isolate it.

Fix 2: Restart the DNS Client Service

If switching DNS did not resolve the error, check whether the Windows DNS Client service is actually running. A quick way to confirm: in Command Prompt run nslookup google.com 8.8.8.8 — this queries Google's server directly, bypassing the local service. If that works but nslookup google.com alone fails, dnscache is the problem.

1. Press Win + R, type services.msc, and press Enter.
2. Scroll to DNS Client.
3. Right-click → Restart. If Restart is greyed out, the service is protected and must be restarted from the command line.

In an elevated Command Prompt:

After restarting, run nslookup google.com again to confirm resolution is restored. On some Windows 11 builds dnscache is marked as a protected service and the GUI Restart button is permanently disabled — the command line approach bypasses that restriction.

Fix 3: Reset the TCP/IP Stack and Winsock

A corrupted network stack produces identical symptoms to a broken DNS configuration. It is less common but worth ruling out when Fixes 1 and 2 have both failed. Open an elevated Terminal (right-click Start → Terminal (Admin)) and run all five commands in order:

Restart the PC after all five commands complete. The reset rewrites the TCP/IP registry keys and rebuilds the Winsock catalog from scratch. You will not lose saved Wi-Fi passwords, firewall rules, or static IP assignments. After the reboot, verify with nslookup google.com before opening a browser.

Fix 4: Disable IPv6 on the Adapter to Isolate IPv6 DNS Failures

Windows 11 sends DNS queries to the IPv6 resolver first when IPv6 is enabled. If your router hands out an IPv6 prefix via DHCPv6 or SLAAC but has no working IPv6 DNS upstream, every single lookup stalls for four to eight seconds waiting for the IPv6 query to time out before the IPv4 fallback runs. On some network configurations the fallback never executes and the result is a hard DNS failure with no obvious cause.

To test whether IPv6 is the culprit, temporarily disable it on the adapter:

1. Open Settings → Network & Internet → Advanced network settings.
2. Click More adapter options to open the classic Network Connections window.
3. Right-click your adapter → Properties.
4. Uncheck Internet Protocol Version 6 (TCP/IPv6).
5. Click OK and test DNS resolution with nslookup google.com.

If disabling IPv6 clears the error, the correct long-term fix is to configure working IPv6 DNS addresses as described in Fix 1, not to leave IPv6 disabled permanently. Disabling IPv6 breaks certain Windows features and some applications depend on it being active.

Fix 5: Update or Roll Back the Network Adapter Driver

Driver-level failures cause intermittent DNS errors that are indistinguishable from DNS server problems at the application layer. This is particularly common on Intel Wi-Fi 6 adapters, Realtek Gigabit Ethernet controllers, and Killer networking hardware after in-place upgrades to Windows 11.

1. Press Win + X → Device Manager.
2. Expand Network adapters.
3. Right-click your Wi-Fi or Ethernet adapter → Update driver → Search automatically for drivers.
4. If Windows reports the driver is already current, visit the adapter manufacturer's support site directly — Intel, Realtek, Killer, or Broadcom — and download the latest driver package for Windows 11. Windows Update frequently lags behind vendor releases by months for network adapters.

If the problem started immediately after a Windows Update, roll back instead: right-click the adapter → Properties → Driver tab → Roll Back Driver. This restores the previous working version and is fully reversible.

Fix 6: Reboot and Update Your Router

If DNS fails on every device on your network — not just your Windows 11 PC — the problem is upstream of your computer. A hard power cycle clears stuck DNS relay state in the router's firmware:

1. Unplug the router's power cable from the wall outlet.
2. Wait a full 30 seconds.
3. Plug back in and wait for all indicator lights to stabilize, typically 60 to 90 seconds.
4. Test DNS on your PC and at least one other device to confirm the fix is at the router level.

If the problem returns within hours or days, log in to the router's admin panel and check for a firmware update. Default admin URLs by brand (verify on your router's label if you changed the default IP):

• TP-Link: tplinkwifi.net or 192.168.0.1
• ASUS: asusrouter.com or 192.168.1.1
• Netgear: routerlogin.net or 192.168.1.1
• Linksys: linksyssmartwifi.com or 192.168.1.1
• Xiaomi / Mi: miwifi.com or 192.168.31.1
• Netgear Orbi: orbilogin.com
• Most other brands: 192.168.0.1 or 192.168.1.1

Firmware update menus vary by brand and firmware generation — look under labels such as Administration, Advanced, Maintenance, or System. On OpenWrt, update via System → Firmware Upgrade. On DD-WRT, use Administration → Firmware Upgrade.

While in the admin panel, check what DNS addresses your router distributes via DHCP. Look under DHCP or LAN settings. If the router is distributing its own LAN IP as the DNS server and its upstream DNS is broken, setting DNS manually on your Windows 11 adapter as described in Fix 1 is the right workaround until the router firmware is patched or replaced.

Fix 7: Check VPN, Antivirus DNS Hooks, and Firewall Rules

VPN clients, DNS-based ad blockers, and antivirus products with web shield features insert themselves into the DNS resolution path. When any of these components crashes, loses its configuration, or conflicts with an OS update, DNS stops working for the entire system, not just one app.

1. Disconnect your VPN client if one is active and test DNS immediately with nslookup google.com.
2. Open your antivirus dashboard and temporarily disable Web Shield, DNS Protection, or equivalent network filtering features.
3. Test DNS again.
4. If DNS works with those features off, update the security software. Stale versions frequently conflict with Windows 11's DNS-over-HTTPS implementation, which was significantly expanded in recent Windows 11 feature updates.

For Windows Defender Firewall specifically: open Windows Security → Firewall & network protection → Advanced settings → Outbound Rules and scan for any rule blocking UDP port 53 or TCP port 53. Rules left over from an IT group policy, a VPN kill switch that was not cleaned up, or a previous security script are the most common finds in this list.

Verifying the Fix from the Command Line

After any fix, confirm DNS is fully operational before closing your troubleshooting session. Run these three commands in an elevated Terminal:

The first command queries your currently configured DNS server. The second bypasses it and queries Google's public resolver directly — if the second works but the first fails, your configured DNS server address is still wrong or unreachable. The third command shows exactly which DNS server Windows is using on each adapter, which can reveal a stale DHCP assignment that survived the earlier configuration changes.

For more detailed diagnostics, use PowerShell:

Get-DnsClientServerAddress lists the DNS server assigned to every network interface including both IPv4 and IPv6 entries. This is the most reliable way to confirm which resolver Windows 11 will actually send the next query to, because it reads the live adapter state rather than the saved settings UI, which can lag behind a DHCP change.

2026 Considerations: DoH, DoT, and DNSSEC

Windows 11 has included native DNS-over-HTTPS (DoH) support since version 21H1. As of 2026, a growing number of enterprise networks and consumer ISPs also deploy DNS-over-TLS (DoT) at the router or modem level. Encrypted DNS transports improve privacy but introduce a failure mode that plain-text DNS does not have: if the DoH HTTPS endpoint is unreachable, the TLS certificate is rejected, or the endpoint returns an unexpected response, Windows may fail to resolve names entirely and report "DNS server not responding" even though the underlying resolver is healthy and reachable on port 53.

To check and adjust your DoH configuration:

1. Go to Settings → Network & Internet → [connection] → DNS server assignment → Edit.
2. Under each DNS server address field, look for the DNS over HTTPS dropdown.
3. If it is set to On (automatic template) or a custom DoH URL and DNS is failing, switch to Off temporarily to isolate whether DoH is the problem.
4. If disabling DoH restores DNS, verify that the IP address you entered actually corresponds to a DoH-capable endpoint — not all public DNS resolver IPs support the automatic template URL that Windows 11 constructs internally.

DNSSEC validation failures are a separate source of apparent DNS outages. When a domain has a broken DNSSEC signature chain and your resolver enforces validation, queries return SERVFAIL rather than the actual DNS record — indistinguishable from a server being down. You can confirm by querying a non-validating resolver and comparing. If a domain resolves on one resolver but returns SERVFAIL on another, the domain's DNSSEC chain is broken and the fix belongs to the domain owner, not your local Windows configuration. For a thorough explanation of how the DNS resolution chain works end to end, Cloudflare's DNS reference covers recursive resolution, DNSSEC, and DoH in accurate detail.

Common Misdiagnoses

• "My internet is down." DNS failure breaks name resolution but leaves IP connectivity intact. Run ping 8.8.8.8 — if it replies, your connection is healthy and only DNS is broken. The fix path is completely different depending on which is true.
• "It must be malware." DNS hijacking by malware exists but is uncommon on a patched Windows 11 system with Windows Defender active. Exhaust configuration-based causes before running a full scan.
• "The router rebooted and its IP changed." If a power cycle changes the router's gateway address, Windows may hold a cached DHCP lease pointing to a DNS server IP that no longer exists. Run ipconfig /release then ipconfig /renew to force a fresh lease with current DNS addresses.
• "Windows Update broke it." Feature updates sometimes reset adapter-level DNS settings back to DHCP, silently overwriting manually configured server addresses. After any major update, go back to DNS server assignment and confirm your entries are still present.
• "It only happens on Wi-Fi, not Ethernet." Wi-Fi-only failures point to the wireless adapter driver, the access point, or differing DHCP settings between the 2.4 GHz and 5 GHz SSIDs. If your router broadcasts both bands as separate networks, confirm the DHCP DNS settings are identical on both.

How to Prevent Recurrence

• Set DNS manually at the adapter level as described in Fix 1, rather than accepting whatever the router hands out via DHCP. This removes the router and ISP from the DNS path entirely.
• Keep router firmware updated — DNS relay bugs are among the most frequently patched issues in consumer router firmware releases.
• Update network adapter drivers from the manufacturer's site on a quarterly basis rather than waiting for Windows Update to push them.
• Keep VPN clients, DNS ad blockers, and antivirus software updated in lockstep with Windows 11 feature updates. Compatibility lag after major updates is the single most predictable trigger for post-update DNS failures.
• Run ipconfig /flushdns after making any DNS zone change yourself. Stale cache entries serve old records for the full TTL duration and can make a correct zone appear broken.