Few error messages are more frustrating than “DNS server isn’t responding” or “This site can’t be reached” — especially when your Wi-Fi icon shows a full signal and every other app seems fine. Your internet is connected, yet websites simply will not load.
DNS is one of those invisible systems you never think about until it fails. The good news is that DNS errors are among the easiest connection problems to fix yourself. Most are solved in under ten minutes with a restart, a cache clear, or one settings change that also makes your browsing slightly faster and more private.
This guide explains what DNS does, why it breaks, and a clear sequence of fixes to work through from simplest to most thorough.
Quick Answer
DNS errors mean your device cannot translate a website’s name into its numerical address. Fix them by restarting your router and device, flushing the DNS cache, and changing your DNS server to a fast public service such as 1.1.1.1 or 8.8.8.8 in your device or router settings. If only one website fails, the problem is usually that website, not your connection.
What DNS Does and Why It Breaks
Computers reach websites using numerical IP addresses, but humans remember names like a news site or a shop. DNS — the Domain Name System — is the translator between the two, often compared to a phone book for the internet. As Cloudflare’s introduction to how DNS works describes, every website visit begins with this lookup, usually in a fraction of a second.
When DNS fails, the lookup fails, and your browser reports errors such as DNS_PROBE_FINISHED_NXDOMAIN, DNS server not responding, or ERR_NAME_NOT_RESOLVED. Common causes include your provider’s DNS servers having an outage, a corrupted cache on your device, router glitches, wrong settings after installing a VPN or security app, or an antivirus or firewall blocking the lookup.
First, work out how big the problem is
- Try three or four different websites. If only one fails, that site is probably down — wait and try later.
- Try a second device on the same Wi-Fi. If it works, the problem lives on the first device.
- If no device can load anything, the problem is your router or your provider’s DNS service.
This two-minute diagnosis tells you exactly which fixes below apply to you, and saves you changing settings on a healthy device when the router is at fault.
Fix 1: Restart Everything Properly
It is a cliché because it works. A restart clears temporary DNS failures cached by your router and gives every device a fresh start.
- Turn off your router at the power socket — do not just press a standby button.
- Wait a full 30 seconds so the connection at the provider’s end resets.
- Turn the router back on and wait two to three minutes until the lights show a stable connection.
- Restart the device that had the problem, then test again.
If websites load now, you are done. Routers that run for months without a restart accumulate small errors, and DNS lookups are often the first thing to suffer.
Fix 2: Flush Your DNS Cache
Your device stores recent DNS answers to save time. If an old or corrupted entry is stored, your browser keeps trying a wrong address even though the real one has changed. Flushing forces fresh lookups.
On Windows
- Press the Windows key, type cmd, right-click Command Prompt, and choose Run as administrator.
- Type ipconfig /flushdns and press Enter.
- You should see a message confirming the DNS Resolver Cache was successfully flushed.
- Also try ipconfig /release followed by ipconfig /renew if problems continue.
On Mac and Chrome
On a Mac, open Terminal and run the command sudo dscacheutil -flushcache, then enter your password. In Chrome on any system, type chrome://net-internals/#dns into the address bar and clear the host cache. Afterwards, fully close and reopen your browser before testing.
Fix 3: Change Your DNS Server
This is the fix that solves most stubborn cases. By default you use your provider’s DNS servers, and when they are slow or down, every lookup suffers. Switching to a fast public DNS is free, safe, and easy to reverse.
The addresses to use
Set your primary DNS to 1.1.1.1 and secondary to 1.0.0.1 for Cloudflare, or primary 8.8.8.8 and secondary 8.8.4.4 for Google. The setup instructions for Google Public DNS cover every operating system in detail if you want a second reference while you work.
Change it on your device
- Open your network settings and find the properties for your Wi-Fi or Ethernet connection.
- Locate the DNS settings, often labelled IP assignment or DNS server assignment.
- Switch from automatic to manual, enter 1.1.1.1 as primary and 1.0.0.1 as secondary.
- Save, disconnect and reconnect to the network, then test several websites.
Change it on your router — the better option
Changing DNS in your router fixes the whole house at once: phones, consoles, and smart TVs included. Log in to the router admin page, find DNS settings under the Internet or WAN section, enter the same addresses, save, and let the router restart. Our step-by-step guide to changing DNS settings on your router walks through the menus on the most common router brands.
Fix 4: Check the Usual Suspects
If DNS errors survive all three fixes, check these four causes before assuming anything serious. Temporarily disable your VPN and test again — VPN apps often leave broken DNS settings behind when they disconnect. Pause your antivirus web protection briefly to see if it is blocking lookups. Try a different browser; if it works, clear the original browser’s cache or reset it. And check the date and time on your device: a badly wrong clock breaks the security certificates that websites rely on, which can look like a loading failure.
Common Mistakes to Avoid
The most common mistake is changing DNS settings in five places at random, which makes it impossible to know what fixed — or broke — things. Change one thing, test, then move on. Another is copying DNS addresses from random forums; only use well-known public services like 1.1.1.1 and 8.8.8.8, because a malicious DNS server can redirect your browsing. People also forget that a single failing website is usually that website’s problem, not theirs. Finally, do not factory-reset your router as a first resort: you will lose your broadband login details and Wi-Fi settings, turning a ten-minute fix into an hour of reconfiguration.
Conclusion
DNS errors look alarming, but they are usually temporary and entirely fixable. Start by checking whether the problem affects one site, one device, or everything. Restart the router, flush the cache, and switch to 1.1.1.1 or 8.8.8.8 — that sequence resolves the overwhelming majority of cases. If every fix fails on every device, contact your provider, because the fault is then almost certainly on their network.
Frequently Asked Questions
Is it safe to change my DNS server to 1.1.1.1 or 8.8.8.8?
Yes. Both are long-running public services operated by Cloudflare and Google respectively, used by millions of people. The change is fully reversible — switch the setting back to automatic at any time — and it does not affect your broadband contract or your provider’s service.
Will changing DNS make my internet faster?
It can make websites start loading faster, because the lookup itself happens quicker, especially if your provider’s DNS is slow. It does not increase your download speed for files or streaming; it removes a delay at the start of each new website visit.
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It means the DNS lookup returned “non-existent domain” — the address for that name could not be found. Causes range from a simple typo in the address, to the website being down or moved, to a faulty cached entry on your device, which a cache flush and a DNS change usually clear.
Why do websites load on my phone’s mobile data but not on Wi-Fi?
Mobile data uses your phone network’s own DNS servers, while Wi-Fi uses your router and provider. If mobile data works, your connection hardware is fine and the fault sits with your home DNS path — restart the router and change its DNS settings to fix every device at once.
How often should I restart my router to prevent these errors?
A restart every month or two is a healthy habit, and many routers offer a scheduled automatic reboot in their settings, which you can set for the middle of the night. If you get DNS errors weekly, though, that pattern suggests a failing router or provider issue worth reporting rather than endlessly restarting.
Leave a Reply