"DNS Server Isn't Responding" on Windows 11? How to Fix It

Web pages won’t load and the Windows troubleshooter reports that your DNS server isn’t responding.

Why: DNS turns names like example.com into IP addresses. When the resolver Windows is pointed at stops answering — a stale local cache, a flaky ISP DNS server, or a corrupted network stack — the connection looks alive but nothing loads.

Fix 1: Run the network troubleshooter and flush DNS

Start with the fastest cleanup.

1. On Windows 11, open the Get Help app, type connect to network and internet in the search bar, and select Run network diagnostics. Let it apply any fixes it finds.

2. Then click Start, type cmd, right-click Command Prompt, and choose Run as administrator.

3. Clear the stale resolver cache:

   ipconfig /flushdns

Retest in your browser. A corrupted cache is the most common cause and this clears it.

Fix 2: Test an actual DNS query

In Command Prompt, run ipconfig /all and inspect the DNS Servers listed for the active adapter. There may be multiple IPv4/IPv6 entries; do not use a filter that hides continuation lines.

Then query a known public name against the configured resolver. Example only: if that resolver is 192.168.1.1, run:

nslookup example.com 192.168.1.1

Use your actual resolver address. Check whether it returns records, an authoritative error or a timeout. Compare with another permitted resolver only if network policy allows it; a VPN/corporate resolver may be needed for internal names.

Ping is an optional ICMP connectivity clue. A resolver can ignore ping and still answer DNS, so a failed echo request alone is not a reason to replace it. If actual DNS queries time out, investigate the connection, resolver and UDP/TCP 53 filtering before choosing a change.

Fix 3: Switch to a reliable public DNS server

Point Windows at a public resolver instead of your ISP’s.

1. For Wi-Fi: Settings > Network & internet > Wi-Fi > Manage known networks, then select your network. For Ethernet: Settings > Network & internet > Ethernet, then select the connection.
2. Next to DNS server assignment, click Edit, choose Manual, and turn on IPv4.
3. In Preferred DNS enter 8.8.8.8 and in Alternate DNS enter 8.8.4.4 (Google), or use 1.1.1.1 / 1.0.0.1 (Cloudflare).
4. Leave DNS over HTTPS at its default unless you specifically want encrypted DNS, then click Save.

Fix 4: Reset the network stack

If a fresh DNS server still doesn’t respond, the network stack itself may be corrupted.

1. In an elevated Command Prompt, run these in order:

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

2. Restart the PC so the changes take effect.

FAQ

Other devices on the same network work fine. That suggests a PC-specific configuration or connection condition, but different devices can use different resolvers. Compare the actual DNS server/query results before ruling the router or resolver out.

The error came back after I set a manual DNS. Recheck that you typed the addresses correctly and turned on the IPv4 toggle; a typo leaves Windows with no working resolver.

Should I use DNS over HTTPS? It’s optional. It encrypts your DNS lookups, but it’s not required to fix “DNS isn’t responding” — leave it Off if you’re unsure.

Sources: Microsoft — Fix Wi-Fi connection issues in Windows · Microsoft — Essential network settings, including TCP/IP and DNS