DNS Server Not Responding on Windows 11 How to Fix It

You open Chrome or Edge, and Windows 11 stares back at you with a blank page and the message "DNS server not responding." Your internet connection shows as connected, your router lights look fine, and every other device on the same Wi-Fi seems to be working. This specific error means your PC cannot reach a DNS resolver to translate domain names into IP addresses — and until that is fixed, no website will load. The good news is that this is almost always solvable in under ten minutes, and the fixes are well-defined. This guide walks through every cause and every fix, in order of how likely each one is to solve your problem.

What the Error Actually Means

When Windows 11 runs the built-in network troubleshooter and reports "DNS server not responding," it has already confirmed that your network adapter has an IP address and a default gateway (your router), but a DNS query sent to the configured resolver returned no answer within the timeout window. The resolver can be your ISP's DNS server, a public DNS server like 8.8.8.8, or your router acting as a DNS forwarder. Any one of them being unreachable, overloaded, or misconfigured produces this exact error.

Common Causes

• The DNS server address assigned by DHCP is wrong or the ISP's resolver is temporarily down
• Windows DNS Client service has crashed or is in a bad state
• The local DNS cache is corrupt
• A third-party firewall or antivirus product is intercepting DNS traffic
• The network adapter driver is outdated or has entered a fault state
• IPv6 connectivity issues causing Windows to prefer a broken IPv6 DNS path
• The router itself is the DNS forwarder and its WAN connection has dropped

Step 1 — Rule Out the Router First

Before touching Windows settings, spend thirty seconds confirming that the problem is not the router or ISP. Open a command prompt (press Win + R, type cmd, hit Enter) and try pinging a known IP address directly:

If those four pings succeed, your internet connection is working and DNS is the only broken piece. If they fail, the problem is upstream — restart your router and modem before continuing. If the pings to 8.8.8.8 succeed but ping google.com fails, you have confirmed a pure DNS issue and the steps below will fix it.

Step 2 — Flush the DNS Cache and Reset Winsock

A corrupted local DNS cache or a damaged Winsock catalog can block resolution entirely. Open an elevated command prompt (right-click Start, choose "Terminal (Admin)" or "Command Prompt (Admin)") and run all four commands in sequence:

After the last command, restart your PC. This is mandatory — the Winsock reset does not take full effect until Windows reboots. Once you are back at the desktop, test browsing again before moving to the next step.

Step 3 — Switch to a Public DNS Server

If your ISP's DNS resolver is down or returning garbage, switching to Google (8.8.8.8) or Cloudflare (1.1.1.1) is the fastest fix. Here is exactly how to do it in Windows 11:

1. Press Win + I to open Settings.
2. Go to Network and Internet, then click either Wi-Fi or Ethernet depending on your connection type.
3. Click on your active network name, then scroll down to DNS server assignment and click Edit.
4. Change the dropdown from Automatic (DHCP) to Manual.
5. Enable the IPv4 toggle.
6. Enter 8.8.8.8 as Preferred DNS and 8.8.4.4 as Alternate DNS (or use Cloudflare's 1.1.1.1 and 1.0.0.1).
7. Click Save.

Open a browser and test. If pages load now, your ISP's DNS was the culprit. You can leave these public DNS servers in place permanently — they are faster than most ISP resolvers anyway.

Step 4 — Restart the Windows DNS Client Service

Windows 11 runs a local DNS Client service (dnscache) that caches responses and handles resolution requests. If it has crashed or hung, DNS will fail silently even with correct server settings. To restart it:

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down to DNS Client.
3. Right-click it and choose Restart. If Restart is greyed out, select Stop and then Start.

You can also do this from an elevated terminal:

Note that on some Windows 11 configurations the DNS Client service is marked as non-stoppable through the GUI — using the terminal commands above bypasses that restriction.

Step 5 — Disable IPv6 on the Adapter (Targeted Fix)

Windows 11 prefers IPv6 when available. If your router or ISP advertises IPv6 but the IPv6 DNS path is broken, every DNS query can time out before Windows falls back to IPv4. Disabling IPv6 on the adapter forces it to use only the IPv4 DNS path:

1. Press Win + R, type ncpa.cpl, and press Enter to open Network Connections.
2. Right-click your active adapter and choose Properties.
3. Uncheck Internet Protocol Version 6 (TCP/IPv6).
4. Click OK.

Test browsing. If it works, your ISP has a broken IPv6 DNS delegation — report it to them and leave IPv6 disabled until they fix it. You can also disable IPv6 system-wide via an elevated terminal:

Reboot after running that command.

Step 6 — Update or Roll Back the Network Adapter Driver

A buggy driver update — especially for Intel Wi-Fi 6 AX200/AX201 adapters which are extremely common in Windows 11 laptops — can cause intermittent DNS failures while general connectivity appears fine. Check your driver version:

1. Right-click Start and choose Device Manager.
2. Expand Network Adapters.
3. Right-click your Wi-Fi or Ethernet adapter and choose Properties.
4. Go to the Driver tab. Note the driver date and version.
5. Click Update Driver and choose Search automatically. Alternatively, visit your laptop manufacturer's support page to download the latest driver directly.

If the problem started after a recent Windows Update, click Roll Back Driver on that same Driver tab. Rolling back to the previous driver has solved this problem for a significant number of users after cumulative Windows 11 updates.

Step 7 — Check Your Firewall and Antivirus DNS Settings

Products like Bitdefender, Kaspersky, Norton 360, and Comodo include a "DNS protection" or "Safe DNS" feature that redirects all DNS traffic through their own servers. If those servers become unreachable, DNS breaks for the entire machine. Temporarily disable your third-party security suite and test DNS:

If that resolves successfully while the product is disabled but fails when it is running, log into the security product's settings and either update it, disable its DNS interception feature, or whitelist standard DNS ports (UDP/TCP 53) to pass through unmodified. Use the DNS Lookup tool to verify what your system is actually resolving once the product is back on.

Step 8 — Reset TCP/IP Stack Completely

If none of the above steps have worked, a full TCP/IP stack reset is the next level. This resets all network configuration to Windows defaults, so you will need to re-enter any static IP or DNS settings afterward. From an elevated terminal:

Restart the PC after running all six commands. After reboot, go back to Step 3 and set your preferred public DNS servers manually, because DHCP-assigned DNS from your ISP may be the original source of the problem.

Router-Specific Checks

If multiple devices on your network have DNS failures, the problem is the router, not Windows 11. Access your router admin panel and verify the WAN DNS settings:

• ASUS routers — navigate to http://asusrouter.com or 192.168.1.1, go to WAN > Internet Connection, and set the DNS servers manually to 8.8.8.8 and 8.8.4.4.
• TP-Link routers — navigate to http://tplinkwifi.net or 192.168.0.1, go to Advanced > Network > Internet, and override the DNS fields.
• Netgear routers — navigate to http://routerlogin.net or 192.168.1.1, go to Advanced > Setup > Internet Setup, and enter custom DNS servers.
• D-Link routers — navigate to 192.168.0.1, go to Setup > Internet and look for the DNS server fields under your connection type.

Also check whether your router's firmware is current. Router manufacturers regularly patch DNS relay bugs. A ten-minute firmware update has solved persistent "DNS server not responding" complaints for entire households.

How to Verify DNS Is Working Correctly

Once you have applied a fix, do not just open a browser — browsers cache redirects. Use the command line to verify DNS resolution directly:

Each command should return one or more IP addresses within one second. If you see "Server: UnKnown" or timeouts, DNS is still broken. Also run ipconfig /all and confirm that the DNS Servers field shows the addresses you configured — not old ISP addresses from a stale DHCP lease.

Preventing the Problem From Coming Back

Set a static DNS entry rather than relying on DHCP, use two resolvers (primary and secondary) from different providers so you have automatic failover, and keep your network adapter drivers up to date by checking Device Manager after each major Windows Update. If you are on a laptop that frequently moves between networks, consider pinning your DNS settings in Windows rather than letting each new network push its own resolver — public resolvers like 1.1.1.1 and 8.8.8.8 are accessible from virtually any network worldwide. Finally, if you manage a home network, set firmware update reminders for your router every three to six months. Most DNS intermittency at the home level traces back to aging router firmware handling DHCP and DNS forwarding in unexpected ways.