DNS Server Not Responding? What It Means and How to Fix It

When the Page Won’t Load but the Connection Seems Fine

You try to open a website and get an error instead of the page. Depending on your browser or operating system, it might read “DNS server not responding,” or a code like DNS_PROBE_FINISHED_NXDOMAIN or DNS_PROBE_FINISHED_NO_INTERNET. The confusing part is that everything else can look normal. Another site might load. Your phone might be online. The Wi-Fi icon shows a full signal, and yet this address simply will not come up.

That combination often points to the step just before the connection carries your request. It turns a website’s name into an address your device can reach. When that step fails, the browser has nowhere to send the request, and the page never loads. In many cases the rest of the connection is fine, which is why other sites or devices still work. But not always. An error like DNS_PROBE_FINISHED_NO_INTERNET, for instance, can mean a broader connectivity problem rather than DNS alone. On its own, the message does not tell you which.

The error message alone does not tell you where the failure is. A “DNS server not responding” message is consistent with several faults: your device, your router, the DNS service your network uses, the website, or your wider connection. This guide works through those possibilities in a sensible order. Each check is meant to establish one thing. By the end, you can tell a DNS problem from a general connection problem and know what is worth changing.

What DNS Actually Does

Every website you visit lives at a numeric address, and your device needs that number to connect. People do not remember numbers well, so the internet lets us type names instead. The Domain Name System, or DNS, translates a name like example.com into an address a device can use. That address, usually an IP address, points to the server behind the name. Cloudflare’s plain-English explanation of DNS is a good primer for the full picture. The short version is enough to troubleshoot with.

Here is what happens when you enter an address. Your browser needs the IP address for that name. It asks a DNS resolver to look it up. Devices usually have basic resolver software and a local cache of their own. For names they have not seen, though, they rely on a configured recursive DNS service to do the real lookup. That service is supplied automatically by the network, usually handed out by your router, which in turn typically points to your internet provider’s DNS. The resolver finds the answer and returns it, your browser connects to that address, and the page loads. All of this normally takes a fraction of a second and happens invisibly.

A Name Failing Is Not a Site Failing

Two ideas from that process matter for troubleshooting. The first is that a name failing to resolve is not the same as a website being down. If the resolver cannot turn the name into an address, your browser is stuck before it ever reaches the site. The site itself can be perfectly healthy. It also works the other way: a name can resolve fine while the website is offline for reasons unrelated to DNS.

The second is caching. Resolvers and your own device keep recent answers for a while instead of looking them up every time, which makes browsing faster. That cache is helpful almost always. Once in a while it holds an answer that has gone stale or wrong. A bad entry can send you to an outdated address, or make a site load incorrectly until it clears. That is a different symptom from “DNS server not responding,” but it is worth knowing about, and caching comes up again in one troubleshooting step.

What “DNS Server Not Responding” Actually Means

At its core, the message means your device asked for a DNS answer and did not get a usable one in time. Beyond that, the wording varies. Windows network diagnostics tend to phrase it as “DNS server isn’t responding.” Chrome shows codes instead, and they do not all mean the same thing. The differences point you in different directions.

DNS_PROBE_FINISHED_NXDOMAIN refers to a nonexistent domain. The lookup completed, and the answer was, in effect, “no such name.” That usually means a mistyped address, or a domain that is expired or misconfigured, not a broken resolver. DNS_PROBE_FINISHED_NO_INTERNET is different. Chrome is reporting that its check found no working internet connection at all, which is a broader problem than DNS. A plain “DNS server not responding” usually means the configured resolver did not answer in time, without saying why. Reading the exact wording is the first small clue about where to look.

What Might Be Causing It

Whatever the phrasing, several things could be behind it, and the message does not tell you which:

• The DNS resolver your network uses is briefly overloaded, down, or unreachable.
• Your device is configured to use a DNS server address that is wrong or no longer valid.
• The router or local network is having a problem that affects how DNS requests are handled.
• Something on the device itself, such as its network settings, is misconfigured.
• A VPN, firewall, security suite, or content filter is interfering with DNS.
• The wider internet connection is down, so nothing resolves.
• The specific domain has its own DNS problem on the website’s side.

These are candidates to investigate, not conclusions. A single error does not prove any one of them. Switching DNS provider, the fix you see recommended most often, helps with some of these and nothing for the others. The point of the steps below is to narrow the list rather than guess.

A Calm Way to Troubleshoot It

The fastest route to a fix is not to try everything at once. It is to run a few checks that each rule something in or out, then act on what they show. Work through them in order and stop when you have found the answer.

Step 1: Is It One Website or Many?

Before touching any settings, try two or three other familiar sites. This one comparison splits the problem in half.

If every site fails, the trouble is broad. It points at your device, your router, your DNS service, or your connection. The later steps help you tell those apart. If only one site fails while others load, the problem is probably specific to that domain or the path to it, not your DNS setup. Websites go offline, misconfigure their own DNS, or block certain networks, none of which you can fix from your end. Try more than one site before you conclude anything. If only one refuses to work, the likely answer is to wait and try it again later.

Step 2: Is It One Device or All of Them?

Next, check another device on the same network. Open the same site on a phone, tablet, or second computer while it is on your Wi-Fi.

If the second device works normally, the issue is more likely specific to the first device, its settings, or its software. If every device shows the same failure, the cause is more likely shared. Suspect the router, the DNS service the network hands out, or the connection into your home.

There is a useful variation here. On a phone, turn off Wi-Fi and load the site over mobile data instead. Mobile data uses a completely different network and a different DNS service. If the site loads there but not on Wi-Fi, that steers you toward your home network rather than the website or your device. It is a comparison, not a fix. The reason to try it is that it isolates your local network from everything beyond it.

Step 3: Is It DNS, or the Whole Connection?

DNS resolution and general connectivity are related but separate. Your device can be online yet unable to resolve names, and it helps to know which you are dealing with.

Here is a quick non-technical version. If apps that keep a live connection still work, such as a messaging app receiving new messages, your device very likely has internet access. A website failing to load then points more toward name resolution than toward a dead connection.

Optional Command-Line Checks

If you are comfortable with a command line, two optional checks go further. Neither is required to benefit from the rest of this guide.

The first is to contact a public IP address directly instead of a name. On Windows, open Command Prompt and run ping 8.8.8.8; on macOS, open Terminal and run the same command. If replies come back while a name still will not resolve, packets are reaching the internet. That is one useful sign the trouble is name resolution rather than a dead connection. It is one check, not proof of the cause. Some hosts deliberately block or deprioritize the kind of traffic ping uses. A failed ping does not mean the connection is down. A successful one does not prove the rest is healthy.

The second is to look up a name directly. Running nslookup example.com on Windows or macOS asks a DNS server to resolve that name and shows you the reply. A normal answer with an address means resolution is working at that moment. An error or a timeout means the lookup failed. The output often names which DNS server was queried, which tells you what your device is actually using. What nslookup cannot tell you is why a resolver is slow or unreachable, only that the attempt did not succeed.

Step 4: Check the Device’s DNS Configuration

Devices normally get their DNS settings automatically from the network, and for most people that is the right setup. Problems creep in when DNS was set manually at some point, perhaps to an address that has since changed or stopped working. A wrong manual entry will cause resolution to fail even when everything else is fine.

It is worth looking at where your DNS settings come from. Automatic means the device uses whatever the network provides. Manual means someone entered specific server addresses, and those addresses are now worth checking.

On Windows 11, DNS lives under Settings, then Network & internet, then your Wi-Fi or Ethernet connection. From there you can view and edit the DNS server assignment. Microsoft’s guide to network settings in Windows walks through the exact screens, which differ slightly between versions. On a Mac, the path is the Apple menu, then System Settings, then Network, then your connection, then Details, then the DNS tab. Apple’s guide to changing DNS settings on Mac describes it for the current release. Menu names shift between releases, so use the official pages for your version rather than assuming one path fits every machine.

Before you change anything here, write down the current values exactly as they are. If a change does not help, you will want to put the original settings back, and those are easy to forget. Change one thing at a time, and retest after each change so you know what actually made a difference.

Step 5: Reconnect or Restart, but Only When It Fits

Restarting is the reflex fix, and it does sometimes work, but doing it first and blindly teaches you nothing. A better approach is to reconnect the single device first: turn its Wi-Fi off and on, or reconnect to the network. That can clear a stuck state on that device without disturbing anything else.

Restarting the router is a bigger step because it affects everyone on the network. Save it for when your earlier checks suggest a shared problem, such as every device failing rather than one site. When you do restart the router, understand what it does and does not tell you. If the problem clears, the restart resolved whatever temporary state had built up. It does not explain why the problem happened, and a fault that returns quickly means the reboot only masked something. There is no need to factory-reset anything at this stage; a reset erases your configuration and rarely addresses a DNS error.

Step 6: Clear the DNS Cache

Your device keeps a local cache of recent DNS answers so it does not have to look them up repeatedly. Now and then that cache holds an entry that is stale or wrong. That shows up more as a site loading incorrectly than as a “DNS server not responding” error. Clearing the cache forces a fresh lookup. Try it when a specific site behaves oddly or will not resolve while the rest of your connection is fine. That is especially worth doing if the site recently moved.

On Windows, open Command Prompt and run ipconfig /flushdns. On current versions of macOS, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, which asks for your administrator password. The macOS command has changed across older releases. If you are on a much older version, check the specific command for it rather than assuming this one applies. Flushing the cache is a narrow tool. It can clear a stale entry. It does not fix a DNS server outage, a router problem, a dead connection, or every browser error. Do not expect it to solve a broad failure.

Step 7: Rule Out VPN, Firewall, and Security Software

Anything that sits between your device and the internet can affect DNS. VPNs route your traffic, and often your DNS, through their own servers. Encrypted DNS settings, firewalls, parental controls, and security suites can all filter or redirect DNS requests. When one of these misbehaves, resolution can fail while the rest of your connection looks fine.

Start by checking the relevant settings rather than switching protection off. Look at whether a VPN is forcing its own DNS. Check whether a security suite or router has a web-filtering or encrypted-DNS feature turned on. See whether parental controls are in play. If you do test by changing something, keep it small and reversible. Disconnect a VPN briefly, or pause one filtering feature, then try the site and switch it back on afterward. A change in behavior tells you where to look; it does not by itself confirm the cause. Do not leave a firewall or security tool disabled to work around a DNS error.

Step 8: Decide Whether to Change DNS Servers

By this point you may be wondering whether to switch DNS providers. Sometimes that genuinely helps, specifically when your currently configured resolver is the thing that is failing. If your assigned DNS service is slow, unreliable, or briefly down, pointing your device at a different resolver can restore name resolution.

It helps to understand the distinction. By default, your DNS comes from your ISP by way of your router, chosen for you. A public resolver is one you configure yourself. The best known are run by Cloudflare, at 1.1.1.1 and 1.0.0.1, and Google, at 8.8.8.8 and 8.8.4.4. Both publish current setup instructions, Cloudflare in its 1.1.1.1 documentation and Google in its Public DNS guide. Most setups let you enter more than one address, so the device has a fallback if the first is unreachable. A second address is not a guaranteed backup, though.

What a DNS Change Can and Cannot Do

Be clear-eyed about what changing DNS does and does not do. It can affect how names resolve, and how quickly the first lookup for a new site returns. That in turn shapes how fast a page seems to start loading. It can also change which services are reachable, what content is filtered, and the privacy of your lookups. What it does not do is widen your connection. Switching resolvers will not raise download throughput, lower your gaming ping, cut packet loss, or steady an unstable Wi-Fi signal. Those depend on the connection itself rather than on name resolution.

A couple of practical notes. Some networks rely on their own DNS service for local features. Parental controls, and workplace or school networks, may depend on a specific resolver to function or to enforce policy. Changing DNS on those networks can break things or run against the rules, so it is not always appropriate. As in the earlier steps, record your original settings first, so you can restore them if the new resolver does not help.

Step 9: When to Contact Your ISP or Network Administrator

Sometimes the problem persists across devices, survives the checks above, and seems to involve your assigned DNS service or shared equipment. At that point it may be out of your hands. That is the point to reach out to your internet provider, or to your network administrator on a managed network. Arrive with specifics rather than “the internet is broken.” Useful details include:

• The exact error message or code you see
• Which websites are affected, and whether others work
• Whether more than one device has the same problem
• Whether it happens on both Wi-Fi and a wired connection
• When the problem started
• Whether it is constant or comes and goes
• Which DNS settings or steps you have already tried
• Whether other internet services, such as apps or streaming, still work

A provider or administrator can look at things you cannot. That includes the health of shared equipment, the availability of the DNS service itself, and the connection upstream of your home. None of the checks above proves the ISP is at fault. A clear record of what you observed is what lets them investigate efficiently.

DNS Problems Versus an Unstable Connection

It is worth separating a DNS error from connection trouble that comes and goes, because they feel similar and get treated as one. A DNS failure stops a site from being located by name; until the name resolves, the page will not load at all. That is different from a connection that resolves names perfectly well but keeps degrading in other ways. Think latency that swings around, probes that fail, or brief drops that interrupt calls and games.

The two can occur independently. A device can resolve every name it is asked for and still sit on a connection that is unreliable minute to minute. And a DNS failure can block websites entirely while the rest of the connection is working normally. Sorting out which one you have keeps you from applying a DNS fix to a stability problem, or the reverse.

If your names resolve but the connection still feels unreliable, that is a different investigation. Observing the connection over time is the way to see it. A tool like StabilityTest watches latency, jitter, failed probes, and drops across a stretch of time. That is useful for spotting instability a single moment would miss. It is not a DNS diagnostic, though, and it cannot identify the cause of a name-resolution error. A clean stability result does not point to DNS one way or the other. Use it when the question is reliability over time. Use the steps in this guide when a name will not resolve. For connection drops specifically, our guide to why an internet connection keeps disconnecting covers that side in more depth.

A Quick Symptom Guide

The table below maps common patterns to where the problem likely sits and what to check next. The middle column is where to look first, not a confirmed cause.

Frequently Asked Questions

What does “DNS server not responding” mean?

It means your device asked a DNS server to turn a name into an address and got no usable answer in time. The name resolution step failed, so the browser had no address to connect to and the page did not load. It does not say why the lookup failed, only that it did. Possible causes include the DNS service your network uses, your device’s settings, your router, interfering software, or the connection itself. That is why a few checks beat a single fix.

Why is my DNS server not responding on only one device?

When one device fails while others on the same network work normally, the problem is more likely specific to that device than to the network. Look at that device’s DNS settings, whether a VPN or security tool on it is interfering, and whether clearing its DNS cache helps. If only one machine is affected, start with its configuration.

Does changing my DNS server make my internet faster?

Not in the way people usually hope. A different resolver can make a first lookup return a little quicker, and it can restore name resolution if your current DNS service is failing. It does not increase your download or upload speed, lower your ping in games, or reduce packet loss. Those depend on the connection itself, not on translating names to addresses. If your speed or stability is the real problem, changing DNS will not address it.

How do I know if it’s DNS or my internet connection?

Check whether your device still has connectivity while names refuse to resolve. If a live app is still receiving data, or ping 8.8.8.8 gets replies, your device is reaching the internet. The trouble is then more likely name resolution. If nothing reaches the internet at all, you are looking at a broader connectivity problem rather than DNS alone. Treat these as clues rather than proof.

Should I flush my DNS cache?

Try it when a specific site will not resolve while the rest of your connection is fine. That is especially true just after the site has moved. A stale cached entry can be the cause. On Windows, run ipconfig /flushdns; on current macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Flushing only clears old local answers, so it will not fix a DNS outage, a router fault, or a down connection. It is a small, safe step, not a cure-all.

Is it safe to use a public DNS server like 1.1.1.1 or 8.8.8.8?

For most home users, yes. Cloudflare’s 1.1.1.1 and Google’s 8.8.8.8 are well-established public resolvers with published setup instructions. Switching to one can help if your assigned DNS service is unreliable. Two cautions apply. Some networks, including workplaces, schools, and setups with parental controls, rely on their own DNS service. Changing it can break features or violate policy. And you should record your original settings first, so you can restore them if the change does not help.