#GoToGetsIT: This article is part of an ongoing series from GoTo’s thought leaders on the frontlines: Our Solutions Consultants deeply understand our customers’ unique challenges and connect the right solutions to meet their goals using GoTo technology. Here, they share their industry knowledge on what it takes to help businesses everywhere thrive in a remote or hybrid world.

DNS errors are one of those issues that can stop your day cold. One minute you're loading a webpage, the next you're staring at "DNS server not responding" or "this site can't be reached," wondering if it's your computer, your Wi-Fi, your ISP, or the internet itself. The good news? Most DNS errors are fixable in a few minutes once you know where to look. Let's walk through what DNS actually is, why these errors happen, what each common message really means, and how to get yourself (or your end users) back online.

What is DNS?

A Domain Name Service (DNS) is the website naming method used to put logical-sounding names on top of IP addresses. Web browsers interact through Internet Protocol (IP) addresses, and DNS translates domain names to IP addresses so browsers can load internet resources. Think of DNS as a pretty mask, covering up an ugly jumble of complex numbers. It's a lot easier to remember a catchy name like CNN.com, Microsoft.com, or GoTo.com than it is to memorize a string of IPv4 numbers like 10.9.75.129, or the newer IPv6 addresses like this Wikipedia example: 2001:0db8:85a3:0000:0000:8a2e:0370:7334.

DNS spares every web user from keeping a complex directory of website address numbers, and instead makes typing a website name into the browser URL bar an act of simplicity. But like any translator, DNS can occasionally get its wires crossed — and that's when you start running into errors.

What is a DNS error?

A DNS error happens when your browser can't translate a website name into the IP address it needs to load the page. The error can come from your device, your router, your ISP's DNS server, or the website itself — which is why "DNS error" is more of a category than a single problem. If something you're typing into the URL bar isn't being translated properly, you're going to see some version of a DNS error message before the page can load.

The fastest way to confirm it really is DNS (and not a wider internet outage) is to skip the website name and try the IP address directly. For example, instead of apple.com, try typing 17.253.144.10 into the browser. If the site loads, your DNS lookup is the problem. If it doesn't, you may have a broader connectivity issue.

You can also open a command prompt — a feature in most support tools, or accessed manually on a Windows machine by typing CMD into the search box on the task bar — and "ping" the site to see if it's reachable:

• If the site is reachable, a tracert 17.253.144.10 will show you where the traffic is hanging up.
• If the site isn't reachable, try another site. If nothing loads, the issue may be with your ISP, and a quick check of their service status page (or a call to their support line) is your fastest path to an answer.

Why do DNS errors happen? 6 common causes

DNS errors almost always trace back to one of these:

1. Your DNS cache is stale or corrupted. Your computer stores recent lookups locally, and if those entries get out of date or corrupted, the browser keeps trying to use bad info.
2. Your router or modem needs a refresh. Routers do their own DNS caching, and a long uptime can lead to stale or jammed DNS routing tables.
3. Your ISP's DNS server is having problems. This is more common than people realize — the resolver your ISP automatically assigns can slow down, time out, or briefly fail.
4. Your DNS settings are misconfigured. Especially on machines where someone has manually changed network settings or where a VPN, security tool, or proxy has overridden the defaults.
5. A VPN, firewall, or antivirus is interfering. Security software can intercept DNS queries, and when it misbehaves, the lookup fails.
6. Malware on the device. Some malware redirects DNS queries to a malicious server. If you keep getting DNS errors after trying everything else, run a scan.
   
   

Common DNS error messages and what they mean

Half the battle is knowing which error you're actually looking at, because the fix is often hiding in the message itself. Here are the most common ones I see come across the support desk: 

 

Error message	What it means	Most likely fix
DNS server not responding	Your OS can reach the network, but the configured DNS resolver isn't answering.	Restart router; switch to a public resolver like Cloudflare 1.1.1.1 or Google 8.8.8.8.
DNS_PROBE_FINISHED_NXDOMAIN (Chrome)	The domain name doesn't exist or can't be resolved.	Flush DNS cache; double-check the URL; try a different resolver.
Server DNS address could not be found	The browser can't translate the hostname at all.	Flush cache; change DNS provider; check VPN/proxy.
Can't reach this page / Can't reach DNS server	The DNS server is unreachable from your device.	Restart network adapter; renew DHCP lease; bypass VPN.
DNS resolution failed / DNS resolve fail	The lookup timed out or returned a server failure (SERVFAIL).	Try a public resolver; check ISP status.
The DNS server couldn't process the DNS request	The resolver got the query but failed to process it.	Restart DNS Client service; clear cache; check firewall.
Could not perform DNS name resolution	Often a Windows logon or Active Directory issue — the machine couldn't resolve a service record.	Verify domain controller reachability and primary DNS on the network adapter.

If you want a quick read on the message you're seeing, find it in the table above and start with that suggested fix. If that doesn't clear it up, the workflow below walks through the rest of the troubleshooting steps in order.

How to fix a DNS error: a step-by-step troubleshooting workflow

If you've confirmed it's not the website and not a known ISP outage, walk through these fundamental steps roughly in order of difficulty and effort.

1. Try a different device or network

   This is the fastest sanity check. If your laptop is throwing a DNS error but your phone on the same Wi-Fi loads the page, the issue is on the laptop. If both devices fail on Wi-Fi but your phone on cellular works fine, the issue is on the network.

2. Restart your router and modem

   Tried and true. Unplug both, wait 30 seconds, plug the modem back in first, wait for it to fully come up, then plug the router back in. This clears stale DNS entries on the router and forces fresh lookups.

3. Reboot your computer

   Also tried and true. It rules out any stuck processes and is especially useful after flushing DNS to make sure the refresh fully takes hold.

4. Clear the DNS cache

   This forces your computer to fetch fresh DNS information the next time you visit a site.

   • Windows: Open Command Prompt and run ipconfig /flushdns
   • macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
   • Chrome browser cache: Visit chrome://net-internals/#dns and click "Clear host cache"

5. Renew your IP / DHCP lease

   If your computer is holding onto a stale network configuration, this gives it a clean one:

   ipconfig /release
   ipconfig /renew

6. Switch to a public DNS resolver

   If your ISP's DNS server is slow or unreliable, switching to a public resolver almost always helps. The two most widely used options are:

   • Cloudflare: 1.1.1.1 and 1.0.0.1 (1.1.1.1)
   • Google: 8.8.8.8 and 8.8.4.4 (Google Public DNS)

   You can set these on your individual computer (in network adapter properties) or on your router so every device benefits.

7. Check your hardware and cables

   Is everything on? Are any cables loose? It sounds basic, but a partially seated Ethernet cable can produce some weird, intermittent DNS behavior.

8. Update your router firmware

   An out-of-date router can have DNS bugs that the manufacturer has already patched. Log into your router's admin page and check for firmware updates.

9. Disable VPN, proxy, or third-party security software temporarily

   If a DNS error appeared right after you installed or updated a VPN, firewall, or antivirus, try disabling it. If the error clears, you've found your culprit.

10. Run a wizard

    On a PC, type "settings" in the search box, find Settings → Troubleshoot, and run the network diagnostics. They'll either self-correct or point you toward what's wrong.

11. Run an antivirus scan

    Rule out any malware that might be hijacking DNS queries.

12. Check DHCP

    DHCP (Dynamic Host Control Protocol) automatically obtains IP info and should be enabled on both your device and your router. You'll typically find it under your local area connection's IP properties. Setting "Obtain DNS server addresses automatically" and "Obtain an IP address automatically" is what you want for most home and small-office setups.

13. Reset the network stack (the nuclear option)

    If nothing else has worked, reset Windows' network configuration completely:

    netsh winsock reset
    netsh int ip reset

    Reboot afterward.

14. Reach out to the experts

    The next time a DNS error suddenly appears on your screen, you can contact your IT department, which might be using a tool like LogMeIn Resolve that has troubleshooting features built into its remote management and support. These include executing a command prompt on your machine from a remote location or jumping into a screen-sharing session to check your settings.

How to fix the "DNS server not responding" error specifically

This is by far the most common DNS error message, and it's worth calling out because the fix order is slightly different than the general workflow. When you see "DNS server not responding," try in this order:

1. Restart your router — this alone fixes a surprisingly high percentage of cases.
2. Switch DNS to 1.1.1.1 or 8.8.8.8 at the device or router level.
3. Flush the DNS cache with ipconfig /flushdns.
4. Disable any VPN or proxy to rule out interception.
5. Try a different browser to rule out browser-level DNS-over-HTTPS settings.
6. Boot into safe mode with networking — if DNS works there, a startup program or driver is interfering.

If those don't work, the issue is more likely upstream (your ISP or the destination's DNS) than on your machine.

DNS troubleshooting commands every IT pro should know

If you're supporting end users, these are the commands worth keeping in your back pocket. Most of them work over a remote command prompt session, which means you don't have to walk a user through typing them.

Command	What it does
ping <hostname>	Tests basic reachability and confirms whether the name resolves to an IP.
nslookup <hostname>	Shows you exactly what DNS server your machine is asking and what answer it's getting back.
nslookup <hostname> 1.1.1.1	Forces the lookup against a specific resolver — perfect for confirming whether your local DNS is the problem.
tracert <hostname> (Windows) / traceroute (macOS/Linux)	Maps the path traffic takes and shows where it stalls.
ipconfig /flushdns	Clears the local DNS resolver cache.
ipconfig /displaydns	Shows what's currently in the DNS cache — useful for spotting bad entries.
Resolve-DnsName <hostname> (PowerShell)	A more detailed lookup with full record types.
dig <hostname> (macOS/Linux)	The Linux/Unix workhorse for DNS troubleshooting; rich output by default.

A typical IT troubleshooting flow is: ping to check connectivity → nslookup against the local resolver → nslookup against a public resolver → tracert if there's a routing issue. That sequence isolates whether the problem is connectivity, local DNS, ISP DNS, or routing.

When the issue is on the server side

If you're an IT admin or MSP responsible for resolving DNS at the infrastructure level, the picture gets a bit broader. The most common server-side DNS issues I see are misconfigured records, expired domain registrations, single points of failure in resolver chains, and DNSSEC validation problems. A few best practices help avoid most of them:

• Always run a primary and a secondary DNS server. Single-resolver dependencies are one of the most common causes of "the whole company can't browse" outages.
• Monitor resolution times, not just up/down status. Slow DNS feels broken to users long before it actually fails.
• Consider DNS-over-HTTPS (DoH) for client devices on untrusted networks.
• Document the DNS provider, account ownership, and renewal dates for every domain. Expired domains and unreachable registrar accounts are surprisingly common root causes for major outages.

When you need backup: remote support tools

The next time a DNS error suddenly appears on someone's screen — yours or an end user's — the fastest path to a fix is often a remote support tool that lets IT execute these commands without disrupting the person on the other end. A platform like LogMeIn Resolve gives IT teams a remote command prompt, screen sharing, and scripted remediation for repeat issues, so most DNS errors can be handled in a few minutes without ever asking the user to read a command back over the phone. For IT teams supporting hundreds or thousands of endpoints, that's the difference between a five-minute fix and a half-day ticket.

Of course, if DNS errors are completely preventing you from reaching the internet on the affected device, you'll need to rely on your own manual walkthrough of the steps above.

FAQs

What is a DNS error?

A DNS error is what happens when your device can't translate a website name into the IP address it needs to load the page. It can come from your device, your router, your ISP, or the website itself — and the fix depends on which.

What causes DNS errors?

The most common causes are a stale or corrupted DNS cache, router or modem issues, an unreliable ISP DNS server, misconfigured network settings, interference from a VPN or security tool, and (occasionally) malware redirecting DNS queries.

Why do I keep getting DNS errors?

If DNS errors keep coming back, the issue is usually persistent — typically a flaky ISP resolver, a misbehaving router, or a security tool intercepting DNS. Switching to a public DNS resolver like 1.1.1.1 or 8.8.8.8 resolves a large share of recurring DNS errors.

How do I fix a DNS error?

Start with the basics: restart your router, flush your DNS cache (ipconfig /flushdns on Windows), and try a different device on the same network to confirm where the problem is. If those don't work, switch to a public DNS resolver and disable any VPN or proxy temporarily.

What does "DNS server not responding" mean?

It means your computer can reach the network but the DNS server it's been told to ask isn't answering. It usually points to either a router issue or an ISP-side DNS resolver problem. Restarting the router and switching DNS to 1.1.1.1 or 8.8.8.8 fixes most cases.

Is it safe to change my DNS server?

Yes — switching to a reputable public DNS provider like Cloudflare or Google is safe and often improves both speed and reliability. Both providers publish their privacy practices, so it's worth a quick read before you switch if privacy is a priority.

What's the difference between a DNS error and an internet outage?

A DNS error means name lookups are failing, but the underlying connection may be fine — you can usually still reach a site if you type the IP address directly. An internet outage means the connection itself is down, so nothing loads regardless of how you address it.