How to Fix “DNS Server Not Responding” Error on Windows (7 Proven Fixes)

Getting “DNS server not responding” on Windows? Fix it fast with 7 proven methods — flush your DNS cache, switch to Google’s 8.8.8.8 DNS, reset TCP/IP, and more. No tech skills needed.

You open your browser, type in a website, and get hit with a frustrating message: “DNS server not responding.” Your Wi-Fi shows connected, everything looks fine — but nothing loads. This error means your computer can’t translate website names (like google.com) into the numeric IP addresses it needs to reach them, a process handled by DNS (Domain Name System), which works like the internet’s phone book.

The good news: this is one of the most fixable Windows errors out there. It’s almost always caused by a stale DNS cache, a momentary router glitch, or a misconfigured DNS setting — none of which require technical skills to fix.

This guide walks you through 7 proven fixes for the “DNS server not responding” error on Windows, starting with the fastest and easiest.

Quick Answer

To fix “DNS server not responding” on Windows, restart your router and flush your DNS cache by running ipconfig /flushdns in Command Prompt (as administrator). If the error persists, switch your DNS server to Google’s (8.8.8.8 / 8.8.4.4) or Cloudflare’s (1.1.1.1 / 1.0.0.1) in your network adapter settings. Most cases are resolved by these three steps alone.

What Causes “DNS Server Not Responding”?

When you type a website address, Windows contacts a DNS server to look up that site’s IP address. If that lookup fails for any reason, you see this error. The most common causes are:

  • Router crash or overload — your router needs a simple restart to clear its memory.
  • Corrupted DNS cache — old or incorrect address records saved on your PC cause the lookup to fail.
  • ISP’s DNS server is down — your provider’s servers are slow, overloaded, or temporarily unavailable.
  • Outdated network adapter driver — the software controlling your Wi-Fi or Ethernet card has a bug.
  • Antivirus or firewall blocking DNS — security software is intercepting and blocking DNS requests as a side effect.
  • Corrupted TCP/IP stack — Windows’ core networking settings have become misconfigured.

7 Fixes for “DNS Server Not Responding” on Windows

Work through these fixes in order. Most people are back online after Fix 1, 2, or 3.

Fix 1: Restart Your Router and Modem

A router restart is the single most effective first step. It clears the router’s memory, drops stale connections, and picks up a fresh DNS assignment from your ISP. If every device in your home is affected — phones, tablets, laptops — this is almost certainly the fix.

  1. Unplug your router (and modem, if it’s a separate box) from the power outlet.
  2. Wait 30 seconds.
  3. Plug the modem back in first. Wait until its indicator lights stabilize — about 60 seconds.
  4. Plug the router back in. Wait another 60 seconds.
  5. Try loading a website on the affected device.

Pro tip: Always unplug the power cable rather than pressing the router’s physical Reset button. The Reset button restores factory settings and wipes your custom Wi-Fi password — unplugging the power does not.

Fix 2: Flush Your DNS Cache

Windows saves DNS lookups in a local cache to speed up browsing, but that cache can become stale or corrupted over time. Flushing it forces Windows to fetch fresh records for every site you visit.

  1. Press Windows key + R, type cmd, then press Ctrl + Shift + Enter to open Command Prompt as administrator.
  2. Type the following command and press Enter:
    ipconfig /flushdns
  3. You should see the message: “Successfully flushed the DNS Resolver Cache.”
  4. Restart your browser and test a website.

Troubleshooting tip: If you see “Access is denied,” you didn’t open Command Prompt as administrator. Close the window, search for Command Prompt in the Start menu, right-click it, and choose Run as administrator.

Fix 3: Switch to Google’s or Cloudflare’s DNS Server

Your ISP’s DNS server may be down or simply too slow. Switching to a fast, reliable public DNS server — like Google’s or Cloudflare’s — is one of the most effective fixes, and it often speeds up your browsing as a bonus.

  1. Press Windows key + R, type ncpa.cpl, and press Enter to open Network Connections.
  2. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
  3. Click Internet Protocol Version 4 (TCP/IPv4), then click Properties.
  4. Select Use the following DNS server addresses and enter:
    Preferred DNS server: 8.8.8.8
    Alternate DNS server: 8.8.4.4
  5. Click OK, then Close. Open a browser and test.

Pro tip: Cloudflare’s DNS (1.1.1.1 / 1.0.0.1) is a strong alternative — it’s consistently one of the fastest DNS resolvers worldwide and has a privacy-first approach that doesn’t log your browsing activity.

Fix 4: Restart the DNS Client Service

Windows runs a background process called the DNS Client service that handles all DNS lookups. If it has frozen or crashed, restarting it can clear the error without any other changes needed.

  1. Press Windows key + R, type services.msc, and press Enter.
  2. Scroll down the list to DNS Client.
  3. Right-click it and select Restart.
  4. If Restart is greyed out, the service is managed automatically by Windows — move on to Fix 5.

Fix 5: Reset Your TCP/IP Stack and Winsock

The TCP/IP stack and Winsock catalog are the core components Windows uses to communicate on any network. Corruption in either can cause persistent DNS errors. Resetting them is completely safe and takes about two minutes.

  1. Open Command Prompt as administrator (see Fix 2, step 1).
  2. Run each command below, pressing Enter after each one:
    netsh winsock reset
    netsh int ip reset
    ipconfig /release
    ipconfig /flushdns
    ipconfig /renew
  3. Restart your computer once all commands complete.

Troubleshooting tip: If ipconfig /renew returns an error about “media disconnected,” skip it — this is normal for Wi-Fi adapters in certain states and won’t affect the reset result.

Fix 6: Update or Roll Back Your Network Adapter Driver

An outdated or buggy driver can cause intermittent DNS failures. Updating usually fixes it — but if the error started right after a Windows update, rolling back to the previous driver version may be exactly what’s needed.

  1. Right-click the Start button and choose Device Manager.
  2. Expand Network Adapters.
  3. Right-click your Wi-Fi or Ethernet adapter and select Update driver → Search automatically for drivers.
  4. If the error appeared after a recent Windows update, right-click the adapter, choose Properties, open the Driver tab, and click Roll Back Driver.

Fix 7: Temporarily Disable Your Antivirus or Firewall

Some antivirus programs and third-party firewalls intercept DNS requests to scan them — and can accidentally block them instead. Disabling your security software briefly is a safe diagnostic step. Just don’t browse untrusted sites while it’s off.

  1. Right-click your antivirus icon in the system tray (bottom-right corner of your taskbar).
  2. Look for an option like Disable protection, Pause, or Turn off temporarily.
  3. Try loading a website. If it works, your security software is the culprit.
  4. Re-enable protection immediately after the test.
  5. Check your antivirus settings for DNS filtering, “Web Shield,” or HTTPS scanning features and configure an exclusion — or contact the vendor’s support team for guidance.

Common Mistakes to Avoid

  • Pressing the router’s physical Reset button instead of power-cycling it. That button restores factory settings and deletes your Wi-Fi password. Unplug the power cable instead — that’s a power cycle with no side effects.
  • Skipping the “Run as administrator” step in Command Prompt. The ipconfig /flushdns and netsh commands fail silently or return errors without admin privileges. Always right-click and choose Run as administrator.
  • Forgetting to click OK when changing DNS settings. The new DNS servers won’t apply until you click OK in both the TCP/IPv4 Properties and Network Adapter Properties windows. Closing either window without clicking OK discards your changes completely.
  • Testing in the same browser tab after making a fix. Browsers cache their own DNS and page data. Always open a new private/incognito window to test — an existing tab can make you think a fix didn’t work when it actually did.
  • Leaving your antivirus disabled after the diagnostic test. Re-enable your protection immediately once you’re done testing. Never leave your PC unprotected while browsing for longer than a minute or two.
  • Assuming the problem is your PC when every device is affected. If every phone, tablet, and laptop in your home shows the same error, the problem is your router or your ISP — not any individual device. Power-cycle the router first before touching any PC settings.

Frequently Asked Questions

What does “DNS server not responding” mean?
It means your computer sent a request to translate a website name into an IP address, but the DNS server didn’t reply. Without that translation, your browser can’t load websites — even when your Wi-Fi appears to be connected and working.

Why does this error only affect one device?
If other devices on your network work fine, the problem is specific to that computer — likely a corrupted DNS cache, a misconfigured DNS setting, or a driver issue. Start with flushing your DNS cache (Fix 2) and switching to Google’s DNS (Fix 3).

Is it safe to use Google’s public DNS (8.8.8.8)?
Yes. Google’s public DNS (8.8.8.8 / 8.8.4.4) and Cloudflare’s DNS (1.1.1.1 / 1.0.0.1) are free, highly reliable, and trusted by hundreds of millions of users. Either is a solid replacement for your ISP’s default DNS.

Will resetting TCP/IP delete my files or settings?
No. The TCP/IP and Winsock reset only restores Windows’ internal networking rules to their defaults. It has zero effect on your personal files, installed apps, Wi-Fi passwords, or any other settings outside the networking stack.

Can a VPN cause “DNS server not responding”?
Yes. VPNs route your DNS traffic through their own servers, and a misconfigured or failing VPN can trigger this error. Disconnect your VPN and test your connection directly. If the error disappears, check your VPN’s DNS settings or contact their support team.

What if none of the seven fixes work?
Contact your Internet Service Provider. The problem may be a DNS server outage or a fault on their network. Your ISP’s support team can run remote diagnostics on their end that you have no way to access yourself.

Does this error mean I have a virus?
Not typically. The vast majority of DNS errors are caused by router glitches, stale cache, or misconfigured settings — not malware. However, some malware does modify DNS settings. If the error keeps returning after you’ve applied all the fixes, run a full scan with Windows Defender or Malwarebytes as a precaution.

Conclusion

The “DNS server not responding” error sounds technical, but it’s almost always fixable without a technician. A router restart, a quick ipconfig /flushdns command, or a switch to Google’s DNS (8.8.8.8) resolves the vast majority of cases in under five minutes. Work through the fixes in order and test after each one — you’ll be back online fast.

If your problem is broader — your Wi-Fi shows connected but nothing loads at all — read our guide on Wi-Fi Shows Connected But No Internet on Windows 11 for additional network-level fixes. If your connection drops repeatedly throughout the day, see Wi-Fi Keeps Disconnecting on Windows 11 for targeted solutions.