What is Error Code 105 (net::ERR_NAME_NOT_RESOLVED) & How to Fix It?

If you’re using Google Chrome as your default browser, at some point you may come across an Error Code 105 (net::ERR_NAME_NOT_RESOLVED). This error is specific to Google Chrome, so you’ll probably want to know what causes this error message and what are some possible fixes.

What is Error 105? What Causes it?

Error 105 is displayed following a DNS lookup failure, which means that after you enter the URL of the website you’re trying to reach in Google Chrome, the browser tries to translate a website’s name to its Internet address (IP address) by using a Domain Name System (DNS). If the DNS server cannot be reached by the browser, the DNS resolution fails, and an Error 105 is displayed.

Apart from an unresponsive DNS server, the error 105 can also be caused by:

• no connection to the Internet;
• a misconfigured network;
• a firewall that prevents Chrome from accessing the network.

Since the error code does not display the exact cause that prompted it, you’ll have to follow the thread and check for all possible causes.

How to Fix Error Code 105?

As a first step, check if you’re connected to the internet and that you’ve correctly entered the domain or URL in the browser.

If you’re connected to the internet and there are no errors or typos in the URL, try to visit some other unrelated domains (do a random Google search and follow a few links) to see if they work. If they do, it means you have a valid DNS and probably the DNS server of the website you’re trying to access has some issues.

If you cannot access other domains, it could be that your DNS server has some issues and you might want to change your DNS servers.

Here’s how to change your DNS in Windows:

1. Right click on the Wifi icon and select Open Network & Internet Settings;
2. Click on Change Adapter Options;
3. Right click on your active network connection and select Properties;
4. Left-click on Internet Protocol Version 4, then select Properties (If you use IPv6, do this on IPv6 as well);
5. Select Use the following DNS server addresses:, then type in one of the public DNS server addresses from below:

 1.1.1.1 = CloudFlare DNS

208.67.220.220 or 208.67.222.222 = OpenDNS

8.8.8.8 or 8.8.4.4 = Google DNS

If you’re a MAC user, here’s how you can change your DNS:

1. Go to System Preferences → Network;
2. Click Advanced;
3. Click on the DNS tab;
4. Click the + sign (lower left) to add a new DNS server;
5. Type one of the public DNS server addresses listed above;
6. Click Ok, then click Apply.

If you are a webmaster and your site does not work because of this error, then you will have to troubleshoot:

1. Access your website from a different computer/phone to see if only you are affected or all of your visitors;
2. Clear the DNS cache by navigating to chrome://net-internals#dns and press the “Clear host cache” button.

If this still didn’t solve the issue, you might have to check your domain’s nameservers and A records. To do this, you can use tools like digwebinterface.com or https://toolbox.googleapps.com/apps/dig/.

If your domain name is www.example.com, make sure that the root domain (example.com) has an NS record, and that the specified NS e.g. ns1.hosting.com resolves the query “A” example.com.

If it does, make sure that your primary nameserver resolves the FQDN (www.example.com) as well.

If not, add NS and A records. The NS records can be changed at the domain registrar (namecheap.com, godaddy.com, etc.) and must point to the nameservers provided by your hosting company, e.g. ns1.host.net ns2.host.com.

IPv6 Issues

The ERR_NAME_NOT_RESOLVED might be caused because your device connects to an IPv6 network and instead of asking for an “A” record, it asks for an “AAA” record to connect to an IPv6 address.

The DNS server might not handle correctly “AAA” queries or it might respond slowly. In Chrome navigate to chrome://net-internals/#dns and look for the domain name. If you see IPv6 in the Family    this might be the issue.

A fix would be to disable the IPv6 protocol in your Internet Settings.

Here’s how to disable IPv6 in Windows:

1. Right click on the Wi-Fi icon and select Open Network & Internet Settings;
2. Click on Change Adapter Options;
3. Right click on your active network connection and select Properties;
4. Scroll down to Internet Protocol Version 6 (TCP/IPv6), and untick the checkbox;
5. Click Ok to save;
6. Restart your computer.

Here’s how to disable IPv6 on macOS:

First, you’ll need to run a command through the Terminal application. Please be advised that you may have to run this command again in case of any changes to the network preferences since it may revert this setting.

1. Open Finder
2. Click on Application
3. Click on Utilities Folder
4. Double click on Terminal app., and run the following command in the app window to list your network interfaces and their names: networksetup -listallnetworkservices

After you identify the network interface you’re using, type in the following command in the terminal window to disable IPv6 on that interface:

If you’re using Ethernet, type: networksetup -setv6off Ethernet

If you’re using Wi-Fi, type: networksetup -setv6off Wi-Fi

(You may need to use quote marks to envelope the interface name.)

Adult Filters or Country Filters

If you experience ERR_NAME_NOT_RESOLVED errors while you are using a hotel or some other venue’s WiFi, it might be due to the fact that they deploy some sort of adult content filter and the site you are trying to visit might have tripped over some filter settings.

It can be that the site is banned in that country due to legal reasons (e.g. online gambling, Activist forums, etc.)

You can check with other tools like Down For Everyone Or Just Me, if the website is reported to be up, you might want to change the default DNS settings set by your Router (Which usually defaults to the ISP one) to some other public DNS server like CloudFlare 1.1.1.1, Google 8.8.8.8, OpenDNS 208.67.222.222

As you can see fixing an error code 105 carries some degree of difficulty, but hopefully our tutorial has managed to navigate you through some of the possible causes and fixes, so you’ll know what to do next time you’ll come across this error code.