Few error messages cause more instant frustration than “DNS server not responding.” One moment the internet works fine; the next, every page fails to load while the Wi-Fi icon insists you’re connected. The cause is rarely a dead internet connection. Instead, your computer has lost its ability to translate website names into the numeric addresses that servers actually understand. (How to fix a website that will not load)
That translation job belongs to the Domain Name System (DNS), often described as the internet’s phone book. When a DNS query times out, the browser has no idea where to send your request, so it gives up. The good news: most cases trace back to a handful of common culprits, and nearly all of them are fixable in minutes without a technician. This guide walks through the fixes in the order that actually works, from the fastest checks to the deeper repairs.
What “DNS Server Not Responding” Really Means
Every time you type a web address, your device sends a query to a DNS resolver, asking for the matching IP address. Standard DNS queries travel over UDP port 53, with TCP port 53 used for larger responses. If the resolver doesn’t answer within a short window, Windows throws the “not responding” diagnostic. It is a generic timeout message, not a specific diagnosis, which is why the same error can have several different causes.
In practice, the fault usually sits in one of four places: your router, your internet provider’s DNS servers, your own device’s network settings, or a piece of software (like a VPN or a misconfigured static DNS entry) intercepting traffic. The trick is isolating which one before you start changing settings at random.
Start With the Fastest Checks
Before touching any settings, confirm the scope of the problem. This single step saves people hours.
Test other devices on the same network
If your phone loads websites over the same Wi-Fi while your laptop shows the error, the problem is the laptop, not the router or the provider. If every device fails, the router or ISP is the likely source. This one test decides which half of this guide you need.
Restart the router and modem
It sounds almost too simple, but a power cycle clears stale DNS caches and resets hung connections inside the router. Unplug both devices, wait about 30 seconds, plug the modem back in first, then the router. Give it two minutes to reconnect. A surprising share of cases end right here.
Try a different website
Occasionally a single site is down while everything else works, and the browser misreports it. Open two or three unrelated sites. If only one fails, the DNS is fine and the site itself is the problem. That situation calls for a different playbook entirely, closer to fixing a website that will not load than to DNS troubleshooting.
Flush the DNS Cache and Renew Your IP
Your device stores recently resolved addresses in a local cache to speed things up. When that cache holds a corrupted or outdated entry, queries can fail even though the network is healthy. Clearing it is the standard next step.
On Windows, open Command Prompt as administrator and run these commands in order:
- `ipconfig /flushdns` clears the local DNS cache.
- `ipconfig /release` drops your current IP lease.
- `ipconfig /renew` requests a fresh one from the router.
- `ipconfig /registerdns` re-registers your device with DNS.
On macOS, the equivalent is `sudo dscacheutil -flushcache` followed by `sudo killall -HUP mDNSResponder`. On Linux, `sudo systemd-resolve –flush-caches` covers most modern distributions. After flushing, restart the browser and retry a page. If the error vanishes and stays gone, a stale cache was the whole story.
Switch to a Public DNS Resolver
If your provider’s DNS servers are slow or down, pointing your device at a public resolver bypasses them entirely. Two well-known options are Google Public DNS (8.8.8.8 and 8.8.4.4) and Cloudflare’s 1.1.1.1, which launched on April 1, 2018. Both are free and generally reliable.
| Resolver | Primary address | Secondary address | Best for |
|---|---|---|---|
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | Broad reliability, speed |
| Cloudflare | 1.1.1.1 | 1.0.0.1 | Privacy focus, low latency |
| Your ISP default | Automatic | Automatic | Local network services |
To change it on Windows, open Settings > Network & Internet > Wi-Fi (or Ethernet) > Hardware properties, find the DNS server assignment, and switch it from Automatic to Manual. Enter the two addresses and save. On macOS, the setting lives under System Settings > Network > Details > DNS.
A common mistake here: people enter a static DNS address once, forget about it, then wonder months later why a hotel or office network misbehaves. If you travel often, note that automatic assignment is usually the safer default, and switch to a public resolver only when you have a reason.
Check for Interfering Software
VPNs, proxy tools, and some antivirus suites route or filter DNS traffic. When they misbehave, the resolver never gets a clean answer. If the error appeared right after installing or updating such software, that’s your prime suspect.
Temporarily disconnect the VPN and retry. If pages load, reconnect and check whether the app has a “DNS leak protection” or “custom DNS” toggle that needs adjusting. The same logic applies to proxy settings in the browser or operating system. Reverting DNS to “Obtain automatically” resolves a large share of these cases. (What is the DNS?)
Malware is a rarer but real cause. Some infections modify the hosts file to redirect traffic. On Windows, that file sits at `C:WindowsSystem32driversetchosts`. Open it in Notepad and look for suspicious entries pointing familiar domains at strange IP addresses. Running a full malware scan is worthwhile if you spot anything unusual.
Reset the Network Stack and Adapter
When nothing else works, rebuild the connection from the ground up. Windows offers a one-command reset that reinstalls network adapters and restores default settings:
- Open Command Prompt as administrator.
- Run `netsh winsock reset` and press Enter.
- Run `netsh int ip reset` and press Enter.
- Restart the computer.
You can also disable and re-enable the adapter through Device Manager, or update the adapter driver from the manufacturer’s site. Outdated drivers occasionally cause DNS timeouts on specific hardware, particularly after a major Windows update. If the machine is also sluggish overall, it’s worth checking whether background processes like the antimalware service executable are hogging resources and destabilizing the connection at the same time.
When the Problem Is Bigger Than Your Device
Sometimes the fix isn’t on your end at all. Provider outages, regional routing problems, and even hardware failures at the network level can knock out DNS for hours. Before you spend another evening resetting adapters, check whether others in your area report the same issue. Your provider’s status page or a quick social media search usually tells you. (Decky loader not working steam deck fix 2026)
Big infrastructure changes can also ripple outward. Trade policy and supply chain shifts, such as the debate over semiconductor tariffs on laptops and servers, affect hardware availability and pricing rather than DNS directly, but they’re a reminder that the internet’s plumbing is physical and occasionally disrupted. If you run game servers or hosted services, a separate set of setup issues applies; misconfigured multiplayer backends, for example, follow their own troubleshooting path, much like resolving PlayFab multiplayer server setup problems.
A Quick Diagnostic Order That Saves Time
Most people jump straight to changing DNS addresses, then get lost. A better sequence exists, and it follows the principle of least disruption:
- Test a second device to locate the fault.
- Restart the router and modem.
- Flush the DNS cache and renew the IP.
- Disconnect any VPN or proxy.
- Switch to a public resolver.
- Reset the network stack and update drivers.
- Contact the provider if all else fails.
Following this order means you change one variable at a time. That matters, because changing three settings at once might “fix” the problem while leaving you with no idea what caused it, and no idea how to prevent it next time.
Mistakes That Make Things Worse
A few habits turn a five-minute fix into a week of confusion. Writing down a static DNS address and never recording it is one. Disabling the network adapter and forgetting to re-enable it is another. So is running every “network repair” tool you find, since some of them alter registry settings with no easy undo.
The most common mistake, though, is assuming the error means the internet is down. It doesn’t. Your connection to the router is often perfectly fine. The DNS lookup is what failed, and that distinction points you toward the right fixes far faster than rebooting everything in sight.
FAQ
What causes “DNS server not responding” most often?
The most frequent causes are a stale local DNS cache, a router that needs a restart, a temporary outage at your provider’s DNS servers, or a VPN or proxy interfering with queries. Less commonly, a misconfigured static DNS entry or malware editing the hosts file is responsible.
Does restarting the router really fix it?
Often, yes. A power cycle clears the router’s internal state and forces it to reconnect to your provider, which resolves hung DNS forwarders. It’s the fastest fix to try and costs nothing, so it belongs near the top of any troubleshooting list.
Is it safe to switch to Google or Cloudflare DNS?
Both are widely used public resolvers operated by major companies, and switching is reversible at any time. The main trade-off is that your DNS queries go to that provider rather than your ISP, so review each provider’s privacy policy if that matters to you.
Why does the error appear on one device but not others?
That pattern points to a device-level problem: a corrupted cache, a bad adapter driver, a VPN running only on that machine, or a static DNS setting left over from an earlier configuration. The router and provider are working fine, since other devices resolve names normally.
Can malware cause this error?
It can. Some malicious software modifies the hosts file or changes DNS settings to redirect traffic. If the error appeared suddenly alongside unusual browser behavior, run a full scan and check the hosts file for unfamiliar entries.
How do I know if the problem is my provider?
If every device on the network fails at the same time, and restarting the router doesn’t help, the provider is the likely source. Check their status page or outage reports for your area before continuing to change settings on your own equipment.
Conclusion
“DNS server not responding” looks alarming but is usually one of a few ordinary problems wearing a scary label. The fix almost always starts with a simple test: does another device on the same network work? That answer splits the problem in half and tells you whether to look at your router or your machine. From there, the path is straightforward: restart the hardware, flush the cache, renew the IP, remove interfering software, and only then switch resolvers or reset the network stack.
What makes the difference between a quick recovery and a wasted evening is order. Change one thing at a time, note what you changed, and undo anything that doesn’t help. Keep a public resolver address handy for emergencies, but leave automatic settings in place for daily use. With that approach, the next time the message appears, it becomes a minor inconvenience rather than a mystery, and you’ll be back online before the coffee goes cold.
