Getting a DNS error and can’t reach a website? Learn what DNS errors mean, why they happen, and simple steps to fix them fast.
You type in a web address, hit enter, and instead of the page you want, you see a message about a “DNS” problem. It looks technical and a little alarming, but it’s actually one of the most common and most fixable issues online.
DNS errors happen when your device can’t translate a website’s name into the address computers use to find it. This can be caused by something on your own device, your internet provider, or the website’s own settings.
In this guide, you’ll learn what a DNS error actually is, the different types you might run into, what the most common messages mean, and clear steps to fix or prevent them, whether you’re browsing casually or managing a website of your own.
What Is a DNS Error?
DNS stands for Domain Name System. Think of it as the internet’s address book. Every website has a name people can remember, like example.com, but computers actually communicate using numeric addresses called IP addresses.
When you type a web address into your browser, your device asks a DNS server to look up the matching IP address. A DNS error happens when that lookup fails for some reason, whether the address doesn’t exist, the DNS server can’t be reached, or the records are set up incorrectly.
Like most website problems, DNS errors fall into two general causes. Sometimes the issue sits on your side, such as outdated network settings or a misbehaving router. Other times the issue sits on the website’s side, such as DNS records that were never configured or a domain that lapsed.
Knowing which side the problem is on helps you figure out whether you can fix it yourself in a minute or two, or whether you just need to wait for the site owner to sort it out.
A guide on “Website Errors Explained” for a broader overview of error types
Types of DNS Errors
DNS errors show up differently depending on your browser, device, and what exactly went wrong during the lookup. Here are the main categories you’ll come across.
DNS Server Not Responding
This means your device sent a request to a DNS server, but the server never answered. It often points to a problem with your router, your internet provider’s DNS service, or your own network settings.
DNS_PROBE_FINISHED_NXDOMAIN
Common in Chrome, this message means the browser searched for the domain and came up empty. Usually it’s a typo in the address, or the domain has expired or was never registered.
Server DNS Address Could Not Be Found
This one shows up when the browser can’t locate any DNS server to handle the request at all. It’s frequently tied to network configuration issues on the visitor’s device.
DNS Server Unavailable
This means the DNS server your device is trying to reach is currently down, overloaded, or blocked by a firewall or security setting.
ERR_NAME_NOT_RESOLVED
Similar to NXDOMAIN, this error means the domain name couldn’t be converted into an IP address, often due to incorrect DNS settings on the device or router.
SERVFAIL
This is a technical response from a DNS server indicating it failed to complete the request, often due to a misconfiguration on the server handling that domain.
NXDOMAIN
This response means the DNS server checked and confirmed the domain simply does not exist, at least not with the records currently available.
Common DNS Error Messages and Their Meanings
Here are some of the exact messages you might see, along with what they typically mean.
- DNS_PROBE_FINISHED_NXDOMAIN – The domain doesn’t exist or can’t be found with current DNS records.
- DNS_PROBE_FINISHED_NO_INTERNET – Your device has no active internet connection at all.
- This site can’t be reached (Chrome) – A general message shown when the DNS lookup or connection fails for any reason.
- Server DNS Address Could Not Be Found – The browser couldn’t locate a working DNS server to process the request.
- DNS_PROBE_STARTED – The browser is actively trying to resolve the domain and hasn’t finished yet, though it usually resolves within seconds.
- SERVFAIL – The DNS server tried to process the request but failed, often because of a server-side misconfiguration.
- REFUSED – The DNS server understood the request but refused to answer it, often due to security or access restrictions.
- NXDOMAIN – The domain name does not exist according to the DNS records checked.
- Timeout – The DNS server took too long to respond, so the browser gave up waiting.
How to Fix DNS Errors
The right fix depends on whether you’re a visitor who just wants to reach a page, or a website owner managing DNS settings for a domain.
For Website Visitors
Work through these steps, since most DNS issues clear up within the first few:
- Refresh the page. Some DNS hiccups are just brief delays that resolve on the next attempt.
- Check the spelling of the web address. A single typo can trigger a “domain not found” message.
- Clear your browser’s DNS cache. Old, stored records can conflict with a site’s current setup.
- Restart your router and modem. Unplug them for about 30 seconds, then power them back on.
- Try a different DNS server. Switching to a public option like Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) often solves the issue.
- Try a different device or network. This helps confirm whether the problem is with your setup or the website itself.
- Wait and try again later. If the site’s own DNS records are the issue, it may take time for the site owner to fix them.
Tip: If a DNS error follows you across every website you try to visit, the problem is almost always on your end. If it only happens on one specific site, the issue is likely with that site’s DNS setup.
For Website Owners
If visitors are reporting DNS errors on your website, check these areas:
- Confirm your domain hasn’t expired. An expired domain will stop resolving entirely until it’s renewed.
- Review your DNS records. Make sure A, CNAME, and MX records point to the correct destinations.
- Check your DNS provider’s status page. Outages on their end can affect every domain they manage.
- Verify your nameservers. Make sure your domain is pointed to the correct nameservers for your DNS provider or host.
- Allow time for DNS propagation. Changes to DNS records can take anywhere from a few minutes to 48 hours to fully update worldwide.
- Test with a DNS lookup tool. Free tools let you check exactly how your domain resolves from different locations.
- Contact your DNS or hosting provider. They can confirm whether the issue is a configuration problem or an outage on their servers.
- Set up monitoring for your domain. Alerts let you know the moment your DNS stops resolving correctly.
How to Prevent DNS Errors
A few consistent habits can keep DNS issues from becoming a recurring headache.
- Renew your domain well before it expires. Set a reminder or enable auto-renewal so it never lapses.
- Use a reputable DNS provider. Reliable providers offer better uptime and faster resolution.
- Keep DNS records documented. Know exactly what your records should be in case you need to restore them.
- Limit unnecessary DNS changes. Frequent edits increase the chance of a mistake slipping through.
- Monitor your domain’s DNS status. Automated tools can alert you the moment something breaks.
- Use a secondary DNS service. This adds redundancy in case your primary provider has an outage.
- Double check changes before saving them. A single typo in a record can take a site offline.
- Keep your router’s firmware updated. This helps prevent local DNS issues on home or office networks.
DNS Errors Comparison Table
| Error | Category | What It Means | Common Cause | Who Usually Fixes It |
|---|---|---|---|---|
| DNS_PROBE_FINISHED_NXDOMAIN | Client-side/Domain | Domain not found | Typo or expired domain | Visitor or domain owner |
| DNS Server Not Responding | Client-side | No answer from DNS server | Router or ISP issue | Visitor |
| Server DNS Address Could Not Be Found | Client-side | No DNS server located | Network configuration issue | Visitor |
| SERVFAIL | Server-side | DNS server failed to respond properly | Misconfigured DNS records | Domain owner or DNS provider |
| REFUSED | Server-side | Request denied by DNS server | Security or access restriction | DNS provider |
| NXDOMAIN | Domain-side | Domain does not exist | Expired or unregistered domain | Domain owner |
| Timeout | Client-side or Server-side | No response within expected time | Slow or unreachable DNS server | Visitor or DNS provider |
Frequently Asked Questions
What are DNS errors? They’re messages that appear when your device can’t successfully translate a website’s name into the address needed to reach it.
Why do DNS errors happen? They happen for many reasons, including typos, expired domains, misconfigured records, router issues, or outages at a DNS provider.
Can DNS errors be fixed? Yes. Most are fixable, whether that means restarting your router as a visitor or correcting DNS records as a site owner.
How long does a DNS error take to fix? Simple fixes like clearing a cache take seconds. Larger issues like DNS record changes can take up to 48 hours to fully update everywhere.
What’s the difference between NXDOMAIN and SERVFAIL? NXDOMAIN means the domain doesn’t exist at all, while SERVFAIL means the DNS server tried to respond but hit a technical failure.
Is a DNS error always my fault? No. Many DNS errors come from problems with the website’s own domain or DNS provider, not anything you did.
Which DNS error is the most common? DNS_PROBE_FINISHED_NXDOMAIN is one of the most frequently seen, usually from typos or expired domains.
How do website owners prevent DNS errors? By renewing domains on time, using a reliable DNS provider, documenting records, and monitoring their domain’s status regularly.
Can changing my DNS server help? Yes. Switching to a public DNS service can resolve many lookup issues, especially if your default provider is having problems.
Should I contact my internet provider about a DNS error? If the error happens across every website and other fixes don’t help, your internet provider’s DNS service may be the source, so it’s worth reaching out.
Final Thoughts
DNS errors sound intimidating, but they almost always come down to a simple lookup failure somewhere between your device and the website’s server. Once you understand what’s happening behind the scenes, these messages stop feeling mysterious.
Whether you’re a visitor trying to reach a page or an owner keeping a domain running smoothly, the fixes are usually within reach. Start with the basics, work through the more technical checks if needed, and reach out to your provider when you get stuck.