Troubleshooting

How to fix “DNS Server Not Responding” errors on your browser

by RebootTips

You know that feeling. You open your browser, type in a URL, and instead of a webpage, you get that irritating pause. The spinner just keeps spinning, and then, after what feels like an eternity, the browser tells you “DNS Server Not Responding”. No internet access, nothing. I’ve seen this error pop up on my own machines more times than I care to admit, usually when I’m in a hurry or trying to get something important done. It’s a classic roadblock, and it usually means your system can’t translate those friendly domain names like google.com into IP addresses that computers understand.

Why a measured approach helps

When this error hits, the first thing many people do is reboot their router, or maybe even their computer, and then if that doesn’t work, they throw their hands up and blame the ISP. I get it; it feels like an external problem. But in my experience, jumping straight to the router or the ISP is often a waste of time, or at least it bypasses a lot of quicker, local fixes. My approach is always to start local and work my way out. The goal isn’t just to fix the problem, but to understand where the breakdown is happening so I can avoid it next time, or at least diagnose it faster.

How to get your DNS working again

Here’s how I usually tackle this on my own setup, step by step, focusing on Windows machines as that’s what I primarily use at home, but the principles apply broadly.

Initial Checks: Is it just DNS?

  1. Check your network cable or Wi-Fi connection. This sounds obvious, but sometimes the simplest things are overlooked. Is the Ethernet cable actually plugged in firmly? Is your Wi-Fi connected and showing a strong signal? Look at the network icon in your system tray; any yellow triangles or red X’s?
  2. Try a different device. Grab your phone or another computer on the same network. Can it access the internet? If yes, the problem is likely specific to your machine, which means we can rule out the router or ISP for a moment. If no, then you might be looking at a router or ISP issue, and a router reboot might be warranted after checking everything else on your local machine.

Working with your DNS settings

Now, assuming it’s just your machine:

  1. Flush your DNS cache. Sometimes your local cache gets stale or corrupted. It’s an easy fix:
    • Open the Start Menu, type “cmd”, right-click on Command Prompt, and select “Run as administrator.”
    • In the command prompt, type ipconfig /flushdns and press Enter. You should see a confirmation message.
    • Next, type ipconfig /registerdns and press Enter.
    • Then ipconfig /release followed by ipconfig /renew to grab a fresh IP.

    After these, try your browser again. Sometimes that’s all it takes.

  2. Check and change your DNS server settings. This is often the culprit. Your computer might be trying to use a DNS server that’s down or unreachable.
    • Right-click on the network icon in your system tray (bottom-right of the screen) and select “Open Network & Internet settings.”
    • Click on “Change adapter options” under “Advanced network settings.” This will open the Network Connections window.
    • Find the network adapter you’re currently using (e.g., Wi-Fi or Ethernet). Right-click on it and select “Properties.”
    • In the properties window, scroll down and select “Internet Protocol Version 4 (TCP/IPv4).” Click “Properties.”
    • Here, you’ll likely see “Obtain DNS server address automatically.” If you do, try switching to “Use the following DNS server addresses” and enter public DNS servers. I usually start with:
      • Preferred DNS server: 8.8.8.8 (Google Public DNS)
      • Alternate DNS server: 8.8.4.4 (Google Public DNS)

      Alternatively, you could use Cloudflare’s excellent servers:

      • Preferred DNS server: 1.1.1.1
      • Alternate DNS server: 1.0.0.1
    • Click “OK” on both windows to apply the changes.

    Close and reopen your browser, then try to navigate to a few websites.

  3. Test with nslookup. This is a great diagnostic tool.
    • Open Command Prompt as administrator again.
    • Type nslookup google.com and press Enter.
    • If it returns an IP address, your DNS is likely working, and the issue might be elsewhere (firewall, browser specific). If it fails or times out, you know DNS is still the problem.

Things people often get wrong

I’ve seen a few common pitfalls. One time, I was troubleshooting a laptop with this error, spent ages on Wi-Fi settings, only to realize the user had an Ethernet cable plugged in from a dock that wasn’t connected to the network. Windows was prioritizing the wired connection, which was effectively dead, while the Wi-Fi was perfectly fine. Always double-check which network adapter is active and actually in use. Another common mistake is forgetting to actually click “OK” to apply the DNS server changes in the adapter properties. I’ve stared blankly at a non-working browser, only to realize I clicked “Cancel” or just closed the window. It’s a small detail, but it’ll get you every time. Also, sometimes your firewall or antivirus software might be interfering with DNS requests. Briefly disabling them (if you’re comfortable and know what you’re doing) can help rule them out, but remember to re-enable them.

A systematic approach to network diagnostics always pays off in the long run.

Related Posts