DNS Server Not Responding on Windows: What Is Actually Happening

When Windows shows "DNS server not responding," it means your computer sent a request to translate a domain name (like google.com) into an IP address, but the DNS server it asked never sent a usable answer back. The connection to the internet itself may be fine; what broke is the lookup step that turns human-readable names into the numbers machines actually route to. Most of the time the fix is quick: flush your DNS cache, restart the network adapter, or switch to a more reliable DNS server.

What the error actually means

Every time you type a web address, your PC asks a DNS resolver: "What is the IP address for this name?" That resolver replies with something like 142.250.190.14, and your browser connects to it. The "DNS server not responding" message appears when Windows sends that question and gets silence, a timeout, or a garbled reply.

The key thing to understand: this is a DNS resolution failure, not necessarily a dead internet connection. You can often still ping raw IP addresses while domain names fail completely. If ping 8.8.8.8 works but ping google.com doesn't, DNS is your culprit, not the physical connection.

Why DNS stops responding

The message covers several different underlying problems that all end in the same symptom. The most common causes:

• The DNS server is overloaded or down. Your ISP's DNS server can get swamped or crash, making it look like the server is unavailable.
• A corrupted local DNS cache. Windows stores past lookups. If those cached entries go stale or bad, requests fail before they even leave your PC.
• Wrong or empty DNS settings. A misconfigured network adapter can point at a DNS server that no longer exists.
• Router glitches. Home routers often act as a middleman DNS forwarder. When the router hangs, DNS dies with it.
• VPN, firewall, or antivirus interference. Security software sometimes blocks DNS traffic (UDP port 53) after an update.

Fast fixes that work most of the time

Work through these in order. The first one or two solve the majority of cases.

1. Flush the DNS cache

This clears out stale or corrupted lookup records so Windows fetches fresh answers. Open Command Prompt as administrator and run:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew

The first command wipes the cache. The rest re-register your DNS name and grab a fresh IP lease from your router. Note that ipconfig /release drops your connection for a few seconds until ipconfig /renew runs.

On macOS or Linux? The flush commands are in our DNS propagation guide.

2. Restart your network adapter

A network adapter reset forces Windows to rebuild the connection from scratch:

• Press Win + R, type ncpa.cpl, press Enter.
• Right-click your active adapter (Wi-Fi or Ethernet), choose Disable.
• Wait five seconds, right-click again, choose Enable.

3. Restart the router

Unplug the router, wait 30 seconds, plug it back in. This clears the router's own DNS forwarder cache, which is a frequent hidden cause of a DNS server that appears unavailable.

4. Reset the network stack

If nothing above works, reset Winsock and the TCP/IP stack, then reboot:

netsh winsock reset
netsh int ip reset

Change your DNS server

If your ISP's DNS keeps failing, point Windows at a public DNS resolver instead. This is one of the most reliable long-term fixes. The two most popular free options:

To apply these custom DNS settings on Windows:

1. Open ncpa.cpl and right-click your active connection, then choose Properties.
2. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
3. Choose Use the following DNS server addresses.
4. Enter 1.1.1.1 as preferred and 1.0.0.1 as alternate (or Google's pair).
5. Repeat for Internet Protocol Version 6 (TCP/IPv6) with 2606:4700:4700::1111 and 2606:4700:4700::1001 (Cloudflare), or 2001:4860:4860::8888 and 2001:4860:4860::8844 (Google). Otherwise Windows can keep using your router's IPv6 DNS, and the change can look like it had no effect.
6. Click OK and flush your DNS cache one more time.

Not sure which DNS server you're currently using? Here's how to find your DNS server address in a few clicks.

When the problem is your ISP

Sometimes the fault genuinely sits with your provider. Common ISP DNS problems include:

• Regional outages that knock their resolvers offline for everyone in an area.
• Overloaded servers during peak evening hours that time out under load.
• Recently changed records not yet updated because the ISP resolver is still serving a cached old value. This ties into how DNS propagation works and why new records take time to appear.

Switching to Cloudflare or Google DNS sidesteps most ISP-side issues instantly, because you stop relying on your provider's resolver entirely. If even public DNS fails, the problem is almost certainly your local network or router, not the resolver.

How to confirm DNS is actually fixed

After making changes, verify that name resolution works before assuming you're done. Run this in Command Prompt:

nslookup example.com

A healthy result shows the resolver's address plus one or more IP addresses for the domain. If you see "server can't find" or a timeout, DNS is still broken. You can also verify a domain's records from outside your own machine to rule out a purely local issue. For a deeper look at how domain lookups behave, the MDN DNS glossary and the original RFC 1034 specification explain the resolution flow in detail.

Check if a domain resolves before blaming your PC

When you hit a DNS server not responding error, our DNS Lookup tool queries A, MX, NS, and other records from public resolvers so you can see whether the domain resolves fine outside your machine.

Check a domain's DNS records →