Trusted WordPress tutorials, when you need them most.
Beginner’s Guide to WordPress
WPB Cup
25 Million+
Websites using our plugins
16+
Years of WordPress experience
3000+
WordPress tutorials
by experts

How to Fix ERR_NAME_NOT_RESOLVED in WordPress (Step by Step)

Sometimes, when you try to visit a website, you might see an error message that says ‘ERR_NAME_NOT_RESOLVED’. This means your web browser can’t find the IP address for the domain name you typed.

It’s like trying to call someone whose phone number isn’t in your contacts. You can’t reach them because you simply don’t know which number to call.

This error can be frustrating, but it’s usually easy to fix. Over the years, we have encountered quite a few causes for this problem and have worked out the best steps to take to troubleshoot and resolve the issue.

In this article, we will show you how to easily troubleshoot and fix the ‘ERR_NAME_NOT_RESOLVED’ error in WordPress.

How to Fix ERR_NAME_NOT_RESOLVED in WordPress

What Causes the ‘ERR_NAME_NOT_RESOLVED’ Error in WordPress?

The internet uses a domain name system, or DNS, to make it easier to navigate around the internet. While every website is identified by a unique set of numbers called an IP address, DNS lets you simply type in a domain name that’s easier to remember.

The IP address associated with that domain name will be automatically looked up (or resolved) on a DNS server, and then you will be taken to that address to view the website.

For example, when you type in the domain name wpbeginner.com, a DNS server identifies that the required IP address is 104.18.10.41, and then you are automatically taken to that location to view our website.

The ‘ERR_NAME_NOT_RESOLVED’ error is displayed when something goes wrong with that process and an IP address can’t be found for the domain name you typed.

The ERR_NAME_NOT_RESOLVED Error Message

Without an IP address, your browser won’t be able to find or display the website. If it is your own WordPress website, then you will be unable to add new content, install security updates, and make other important changes.

Depending on the exact situation and the web browser you are using, you may see a similar error message such as:

A number of common issues can cause these error messages, so you will need to troubleshoot the error to fix it. While there may be a problem with the website, this error message is often caused by incorrect settings on your own computer.

Luckily, the error message might suggest a few things you can try, such as checking your internet connection, firewall settings, and DNS configuration.

With that being said, let’s take a look at how to fix ‘ERR_NAME_NOT_RESOLVED’ in WordPress. We recommend starting with the first troubleshooting step since it’s the easiest and then working your way through our guide:

1. Check Your Internet Connection

This error is often caused by a problem on your own computer. So, let’s start with the simplest fix and make sure that you are actually connected to the internet. You might like to visit Google.com and perform a search to make sure your connection is working.

If you can’t access Google or other websites, then the problem is with your internet connection, not the website you are trying to access.

You should make sure that the cables are plugged into your modem and router correctly. You should also try restarting your internet connection by disconnecting your modem and router from the power supply and turning them back on after at least one minute.

If you still see the same error message when trying to visit the website, then you can move on to the next step.

2. Clear Your Browser Cache

Your web browser keeps a temporary copy of everything it downloads to save time when it needs to reaccess those files. This is your browser cache.

The cache can become outdated if the website content has changed after you first accessed it. It can also become corrupted over time. When this happens, you will need to clear the browser cache so that the files are downloaded from the website again.

This can sometimes resolve DNS-related issues, such as the DNS error message you are seeing.

Thankfully, it’s easy to clear the browser cache. For example, in the Google Chrome browser, you simply click on the three-dotted icon in the upper-right corner. Now you can click on ‘More Tools’ and then ‘Clear Browsing Data….’

How to clear the browser cache in Google Chrome

You will need to check the box next to ‘Cached images and files’ on the popup window. Google Chrome will clear the entire cache by default.

With that in mind, you might like to open the ‘Time Range’ dropdown so that it deletes the cached data only from the time period you’ve been seeing the error message.

Fixing the site can't be reached error in WordPress

Make sure you only check the boxes for the data you want to delete. For example, it’s a good idea to delete cookies and other site data, but if you want to keep your browsing history, then you will need to uncheck that box.

When you are ready, click on ‘Clear data’, and Google Chrome will empty the browser cache.

Emptying the Chrome cache

If you are using a different browser, then please see our beginner’s guide on how to clear the browser cache in any browser.

Now, you can try revisiting the website to see if you are still seeing the error message.

3. Clear Your DNS Cache

Besides caching the content of the websites you visit, your computer also stores their IP addresses. This saves time since the browser doesn’t have to look up the same IP address multiple times.

However, the cached DNS information can get outdated, leading to error messages. For example, the cached IP data may be incorrect if the site has moved to a new domain name or moved to a new hosting provider.

You can clear your DNS cache to force your browser to look up the correct IP address for that domain name again.

To help you out, we’ve created a complete guide on how to clear your DNS cache for Mac, Windows, and Google Chrome.

4. Temporarily Disable Your Firewall and Antivirus Software

Antivirus and firewall plugins try to keep you safe by blocking suspicious sites. But unfortunately, they can also sometimes block websites that are trustworthy.

This can happen if your security plugin settings are too strict or the website is set up in a way that triggers the security settings.

You can test whether a firewall or antivirus program is blocking the connection by temporarily disabling the software. If the website now loads without a problem, then you know that the antivirus program or firewall was to blame.

If they are the cause of the problem, then we don’t recommend disabling the software permanently. Instead, you may be able to whitelist the website in the software’s settings so that you can access it while being protected from genuine threats.

If you need help finding these settings, then you can check the software’s official documentation, forums, and social media pages for more information.

Depending on your software license, you may also be able to ask for support by contacting the developer or their customer support team.

5. Change the DNS Server Used by Your Computer

There may be a problem with the DNS server you are using to get the website’s IP address. Many DNS servers are available, and your internet service provider (ISP) assigns one automatically. Sometimes, the server can be unavailable or have the wrong information.

You can switch to a different public DNS server, such as Google Public DNS. You should choose carefully because the DNS provider will be able to see all the websites you visit and may collect your personal information.

Changing Your DNS Server on Mac

Once you’ve decided on a DNS server, you need to add it to your DNS settings. On Mac, you should select the ‘Apple’ icon in the toolbar and click on ‘System Preferences…’

The macOS System preferences...

Next, you should select ‘Network’ from the popup and then click on the ‘Advanced…’ button.

Now, you can open the ‘DNS’ tab.

Fixing the site can't be reached error by changing the DNS server

In the bottom-left corner, you need to click the ‘+’ button.

This adds a new DNS server with a default IP address of 0.0.0.0.

Switching the DNS server settings

Now, you can go ahead and type in the IP address of the public server you want to use. For example, the IP addresses for Google’s public DNS are 8.8.8.8 and 8.8.4.4.

After that, make sure you click on the ‘OK’ button to save your changes.

Switching to a public DNS server to fix the site can't be reached error

This will take you back to the previous popup.

To start using your new DNS server, simply click on the ‘Apply’ button.

How to switch to a different DNS server

Now, you are ready to visit the website to see whether this has removed the error message.

Changing Your DNS Server on Windows

If you have a Windows computer, then you need to go to the Windows Search Box from the taskbar and type in ‘ncpa.cpl’ to go to the Network Connections page.

Go to ncpa.cpl for network connections

Once there, you should right-click the internet connection you are currently using.

Next, select the ‘Properties’ option from the drop-down menu. You may be asked to provide an administrator password. If you don’t know the password, then you will need to contact your IT department or computer admin.

Select the Properties option after right clicking

Now, you should see the ‘Properties’ window.

You need to double-click the ‘Internet Protocol Version 4 (TCP/IPv4)’ option from the list.

Double click the Internet Protocol Version option

This will open up a new window where you need to enable two settings by checking their boxes. These settings are ‘Obtain an IP address automatically’ and ‘Use the following DNS server addresses’.

Now, you can type in the DNS addresses for your public DNS server. The IP addresses for Google’s public DNS are 8.8.8.8 and 8.8.4.4.

Type your preferred DNS

Don’t forget to click the ‘OK’ button at the bottom to store your changes.

Now, you can restart your computer and visit your site to see if the error is resolved.

6. Disable DNSSEC for Your Website Domain

Sometimes, the ‘ERR_NAME_NOT_RESOLVED’ error is caused by problems with the website itself. If your WordPress blog is giving this error, then there are a few things you can try to fix it.

For example, if you have enabled DNSSEC, then it may help to disable it.

DNSSEC stands for Domain Name System Security Extensions. It provides an extra layer of security by protecting your DNS records from unauthorized users.

However, it can also prevent the domain from propagating properly, and this can trigger the ‘ERR_NAME_NOT_RESOLVED’ error.

You can disable DNSSEC from your web hosting account. The way you do this varies depending on your hosting provider, so we will show you how to do it using Bluehost.

In Bluehost, you’ll find the DNSSEC option in the Advanced Tools section under Domains. Simply toggle the ‘DNSSEC’ option to the off position.

Disabling DNSSEC on Bluehost

If you need help disabling DNSSEC, then reach out to your hosting company for support.

And if you are still seeing the ‘ERR_NAME_NOT_RESOLVED’ error after disabling DNSSEC and completing all of the troubleshooting steps in this guide, then it’s time to contact your hosting company’s support team for some expert help.

7. Contact Your WordPress Hosting Provider

If you still can’t access the website after following the steps above, then the website may be temporarily down or experiencing server issues.

If the site belongs to someone else, then there’s nothing else you can do but wait for it to become accessible again.

However, if you are encountering the ‘ERR_NAME_NOT_RESOLVED’ when trying to access your own website, then you should contact your hosting provider for support.

They will be able to help you if there is a technical problem, incorrect settings, an unpaid bill, or some other issue responsible for your website being inaccessible.

Now that you know how to troubleshoot and fix the ERR_NAME_NOT_RESOLVED message in WordPress, you may like to see some other guides related to domain names and DNS:

We hope this tutorial helped you learn how to fix ERR_NAME_NOT_RESOLVED in WordPress. You may also want to see our complete guide to troubleshooting WordPress or our guide to the most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

Disclosure: Our content is reader-supported. This means if you click on some of our links, then we may earn a commission. See how WPBeginner is funded, why it matters, and how you can support us. Here's our editorial process.

Editorial Staff

Editorial Staff at WPBeginner is a team of WordPress experts led by Syed Balkhi with over 16 years of experience in WordPress, Web Hosting, eCommerce, SEO, and Marketing. Started in 2009, WPBeginner is now the largest free WordPress resource site in the industry and is often referred to as the Wikipedia for WordPress.

The Ultimate WordPress Toolkit

Get FREE access to our toolkit - a collection of WordPress related products and resources that every professional should have!

Reader Interactions

5 CommentsLeave a Reply

  1. Suman Sourabh

    I am getting this error as well when I created a new subdomain through cPanel on my WordPress site. Let me see if any of the above fixes the issue. Thanks.

  2. Kzain

    The tip about flushing the DNS cache was particularly useful. Often, outdated cache data can be the culprit behind this error.

  3. Dennis Muthomi

    I have seen this error.
    It appeared more often on a public holidays here in my country.
    I think the error appears because too many users are in their homes trying to access the web and the Internet Service Provider just cant keep up with the user’s connections.
    Could that be also a possibility?

    • WPBeginner Support

      Yes it could be a possibility depending on your local area.

      Admin

    • Jiří Vaněk

      Yes, it’s basically the same as if the server were under a DDOS attack. Except this traffic is probably legitimate, but the server’s performance can’t keep up with the number of users who need a service from the server. And if the server is unavailable, the browser doesn’t receive a response (handshake to establish communication). That’s why this error appears.

Leave A Reply

Thanks for choosing to leave a comment. Please keep in mind that all comments are moderated according to our comment policy, and your email address will NOT be published. Please Do NOT use keywords in the name field. Let's have a personal and meaningful conversation.