DNS Server Not Responding: Easy Fix 2026

You know that moment. You’re mid-scroll, mid-download, or three minutes into a video call, and suddenly… nothing loads. You refresh. Still nothing. Then that little error message pops up: “DNS Server Not Responding.”

Cue the mild panic.

Is your internet down? Did your router die? Did you forget to pay a bill somewhere? Before you spiral into troubleshooting mode and start unplugging everything in sight, take a breath. This is one of the most common — and honestly, one of the most fixable — issues you’ll ever run into online, right alongside classics like Wi-Fi connected but no internet access or a router that keeps disconnecting. It looks scary because it sounds technical, but in reality, it’s usually a small hiccup that takes a few minutes to sort out.

I’ve dealt with this error more times than I’d like to admit, on everything from a five-year-old laptop to a brand-new machine straight out of the box. And nine times out of ten, the fix has nothing to do with your internet plan, your router being “broken,” or some deep hardware failure. It’s almost always something small — a setting, a cache, a driver — that just needs a nudge.

So let’s walk through what’s actually going on, why it happens, and how to fix it step by step, without any unnecessary jargon.

Okay, But What Actually Is DNS (And Why Does It Say “Not Responding”)?

Here’s the simplest way I can explain it. Every website has a “real” address — a string of numbers called an IP address. Nobody wants to type “142.250.190.14” into their browser every time they want to check Google, though, so instead we type “google.com.”

DNS (Domain Name System) is the behind-the-scenes translator that takes the name you typed and converts it into the number your device actually needs to find that website. Think of it like a contacts app on your phone — you tap your friend’s name, and the phone dials the number for you. You never see the number. You just expect it to work.

When you get a “DNS Server Not Responding” error, it means your device tried to make that translation and got nothing back. Silence. The request went out, and no answer came in. Your internet connection itself might be perfectly fine — it’s specifically this lookup step that’s failing.

That distinction actually matters, because it tells you where to focus your energy. You’re probably not dealing with an outage. You’re dealing with a communication hiccup between your device and a specific server.

Why Does This Even Happen?

There’s no single culprit here — it’s usually one of a handful of usual suspects:

• Your network driver is outdated or acting up
• Your DNS settings are misconfigured somewhere
• Your router needs a good old-fashioned restart
• A VPN or antivirus tool is interfering with your traffic
• Your ISP’s DNS servers are temporarily down or overloaded
• Your device’s cached DNS data has gotten corrupted
• A firewall is quietly blocking DNS requests without telling you

The frustrating part is that any one of these can cause the exact same error message, so there’s a bit of trial and error involved. The good news is that the fixes are quick, and you can usually work through them in order without needing to call anyone or install anything complicated. http://router that keeps disconnecting

Let’s Fix It — Step by Step

I’m going to go in order from “takes ten seconds” to “takes a bit more effort,” so you can stop as soon as something works.

1. Just Restart Everything First

I know, I know. “Have you tried turning it off and on again?” feels like the most cliché tech advice on the planet. But it’s cliché because it genuinely works a huge percentage of the time.

Turn off your router. Unplug it if you can. Wait a solid 30 seconds — don’t rush this part, it actually matters for the hardware to fully reset. Plug it back in, let it fully boot up, and restart your computer or phone while you’re at it. Then try loading a website again.

You’d be surprised how often this alone clears things right up.

2. Switch to a Public DNS Server

If the restart didn’t do it, the next move is to try a different DNS server. Your internet provider assigns you one by default, and honestly, some ISPs run DNS servers that are a little… sluggish, or occasionally flaky. Switching to a public one like Google Public DNS or Cloudflare DNS fixes this issue for a lot of people almost instantly.

On Windows:

1. Open Control Panel > Network and Internet > Network and Sharing Center
2. Click Change adapter settings
3. Right-click your active connection and choose Properties
4. Select Internet Protocol Version 4 (TCP/IPv4), then click Properties again
5. Choose Use the following DNS server addresses
6. Enter 8.8.8.8 as the preferred DNS and 8.8.4.4 as the alternate
7. Click OK, then restart your browser

On Mac:

1. Open System Settings > Network
2. Select your active connection and click Details
3. Head to the DNS tab
4. Add 8.8.8.8 and 8.8.4.4 to the list

Give it a minute after changing this, then try loading a page again.

3. Flush Out Your DNS Cache

Your device keeps a little memory bank of recent DNS lookups so it doesn’t have to ask every single time. Handy — except when that memory gets corrupted, which happens more often than you’d think. Clearing it out (called “flushing”) forces your device to start fresh.

On Windows, open Command Prompt as an administrator and type:

ipconfig /flushdns

On Mac, open Terminal and run:

sudo dscacheutil -flushcache

You should see a confirmation message either way. Try your browser again after this. If you’re also seeing slow load times generally, it might be worth reading our guide on how to speed up a slow internet connection as well.

4. Turn Off Your VPN for a Minute

If you’re running a VPN, it might be rerouting your DNS requests somewhere they’re not supposed to go, especially if the VPN app crashed or updated recently. Same goes for some proxy tools. Temporarily disable it and see if that clears things up. If it does, you’ll know the VPN’s DNS settings need a look, or you might just need to switch servers within the app. For a deeper dive, check out our post on choosing the best VPN settings for a stable connection.

5. Update Your Network Driver

This one’s easy to overlook, but an outdated network adapter driver can absolutely cause DNS issues, especially after a Windows update that didn’t play nicely with your hardware.

1. Right-click the Start menu and open Device Manager
2. Expand Network adapters
3. Right-click your adapter and select Update driver
4. Choose Search automatically for drivers

Microsoft also has an official driver update guide if you want to go a bit deeper into this.

6. Try Disabling IPv6

This is a smaller, more niche fix, but it works often enough to be worth mentioning. Sometimes IPv6 and IPv4 settings step on each other’s toes and cause lookup failures.

1. Go to Network Connections
2. Right-click your active connection and select Properties
3. Uncheck Internet Protocol Version 6 (TCP/IPv6)
4. Click OK and restart your browser

You can always re-enable this later if it doesn’t help — it’s not a permanent change.

7. Reset the DNS Settings on Your Router

If this error is showing up on every device in your house, not just your laptop, the problem probably isn’t your laptop at all. It’s your router. Log into your router’s admin panel (usually through a browser at an address like 192.168.1.1) and either reset the DNS settings back to default or manually set them to Google DNS (8.8.8.8) or Cloudflare (1.1.1.1). If you’re not sure how to access your router’s settings, see our step-by-step guide on logging into your router’s admin panel.

8. Peek at Your Firewall or Antivirus

Security software is great at protecting you, but sometimes it’s a little overzealous and blocks legitimate DNS traffic without much explanation. Temporarily disable your firewall or antivirus just to test whether that’s the culprit. If your connection suddenly works, you’ve found your answer — just remember to turn your protection back on afterward and adjust its settings instead of leaving it off.

What If Nothing on This List Works?

If you’ve gone through every step above and you’re still staring at that same error, the issue is very likely on your Internet Service Provider’s end. Their DNS servers might be down, overloaded, or having a rough day. Give them a call or check their outage page — there’s a good chance you’re not the only one experiencing it.

Wrapping It Up

A “DNS Server Not Responding” error looks intimidating the first time you see it, but it’s rarely as serious as it sounds. In most cases, a simple restart or a quick DNS server change will have you back online in a few minutes. Work through the steps above in order, and there’s a very good chance you’ll be back to normal before you even finish your coffee.

If this guide helped you out, save it somewhere handy — because let’s be honest, this error has a way of showing up again when you least expect it.

One last thing worth mentioning: if you’re someone who works from home, streams a lot, or relies on a stable connection for gaming, it might be worth switching to a public DNS server like Google or Cloudflare permanently rather than waiting for this error to pop up again. Public DNS providers tend to have better uptime and faster response times than a lot of default ISP servers, so you may notice slightly snappier browsing as a bonus, not just fewer error messages.

It’s also worth keeping an eye on your router’s firmware. Manufacturers push out updates fairly regularly to patch bugs, including ones that affect DNS handling, and a lot of people never bother checking for these because routers aren’t exactly designed to remind you. A quick login to your router’s admin panel once every few months to check for a firmware update can save you a headache down the line.

At the end of the day, a DNS server not responding error is annoying, but it’s rarely a sign of anything seriously wrong with your device or your internet plan. It’s one of those things that looks worse than it actually is. Work through the fixes above, be a little patient, and you’ll almost certainly be back online well before you expected to be.