One of the most unpleasant situations when trying to access some kind of Internet resource is the appearance of a failure message with the description ERR_NAME_NOT_RESOLVED (error code 105). What kind of error is this, of ordinary users, few people imagine. Nevertheless, it can be eliminated independently and within just a few minutes. Further, basic methods are proposed for consideration, which in most cases are used to eliminate this failure.
Error net :: ERR_NAME_NOT_RESOLVED: reason for occurrence
As for the nature of this error, it is usually referred to situations when the DNS server cannot convert the user request in the form of letters and characters that are entered for the address of a site into a digital interpretation.
The ERR_NAME_NOT_RESOLVED error is equally affected by both stationary Windows-systems and mobile (for the most part this concerns Android, which will be discussed later). Thus, the elimination of the problem just boils down to checking both the DNS service and the settings of the corresponding parameters of the corresponding client.
Initial Troubleshooting Steps
But do not rush to apply the proposed methods below. It may well be that in such a situation a regular reboot will help, and after that the problem will disappear. The same goes for routers if you use a wireless connection to access the Internet. As an additional measure, try to access the requested page from different devices. If the error ERR_NAME_NOT_RESOLVED appears on only one of them, you will have to solve the problem for him. In the event of a failure on all devices, most likely the problems are related to the remote server of the resource itself.
Disabling antivirus and firewall
Often the appearance of this failure is due to the fact that some antivirus programs and built-in protection tools, such as Windows, block the established connection. Many experts note that very often this is noticed by Avast antivirus and some mobile applications.
In any case, try temporarily disabling protection (first an antivirus, then a firewall in the case of Windows platforms) and look at the result. If the problem is in the antivirus, replace it by first completely removing it from the computer in full. For Android systems, the solution is to remove the application initially.
Reset DNS Cache
We will dwell on Android devices separately, but for now, we will consider the methodology for fixing a failure in Windows systems, since the problem here is much more serious. The first solution is to reset the DNS cache, which uses the command line, which must be run with administrator privileges.
First, the ipconfig / flushdns reset command itself is registered in it. After its successful completion, it is mandatory to restart the computer device and check whether ERR_NAME_NOT_RESOLVED fails again. If yes, do the following.
Call the command line again and enter two commands:
- ipconfig / release;
- ipconfig / renew.
After that, as in the previous case, we restart the system and look at the result.
Verify DNS Client Service
In some cases, the error ERR_NAME_NOT_RESOLVED may appear after that. In such a situation, it is necessary to check the status of the service responsible for the correct functioning of the DNS client. It is possible that it may require a restart, and if it is stopped, then a manual start.
For quick access to the appropriate section with the settings, call the "Run" console and write the services.msc command. In the right window we find the corresponding service and look at its status. Even provided that it is currently active (the status is “Running”), use the RMB menu and select restart. If the service is stopped, we enter the editing of parameters (either by double-clicking, or through RMB), we start the service manually with the button of the same name and set the startup type to automatic if something else is set in the options. Upon completion of all operations, we reboot the system.
Using an alternate DNS configuration
But what if the client is fine, the service works, and the error appears again and again? Apparently, the problem is related to the settings of DNS servers.
To change them, we use the properties of the established connection and select the IPv4 protocol settings. In most cases, in particular for wireless connections, automatic reception of addresses should be specified for all options.
If this is the case, but the problem persists, we use an alternative configuration for the primary and preferred DNS server based on the free Google settings, as shown in the image above. After saving the settings, the computer or laptop must be restarted. In the case of a wireless connection, a reboot must also be performed on the router or ADSL modem.
Note: installed for the primary and alternative servers can be interchanged. Sometimes it may be necessary to check the DNS settings on the router.
ERR_NAME_NOT_RESOLVED crash on Android
Finally, a few words about fixing a similar crash on Android devices. In principle, the actions are the same, the only difference is access to the necessary settings and options and section names.
So, to fix the ERR_NAME_NOT_RESOLVED crash on a phone or tablet running an Android system, first go into the settings and go to the Wi-Fi connection. Long press to call up the basic settings and proceed to change the network configuration.
In this section, it is necessary to highlight the option of showing additional parameters, then set the IP settings to “Static”, enter the Google settings in the DNS server fields, as was shown for IPv4 on stationary systems, save the changes and completely reboot the device. In most cases, this approach allows you to get rid of the reappearance of the failure entirely.
Note: before performing these steps, make sure that the device does not turn on airplane mode, since any connection is blocked when using it.
Brief Summary
Speaking of eliminating the problem described above, it is not necessary to follow the decisions in the exact order in which they were presented. You can immediately prescribe an alternative Google configuration, but, of course, only if the DNS service itself is active (for Windows). Without this, absolutely all manipulations will remain inconclusive, no matter how you try.
It remains to add that it would be nice to check your computer or phone for viruses if none of the listed solutions give a result. In extreme cases, to fix the problem on Windows, you can download the 299357 package from the Microsoft website and use it to reset the TCP / IP settings (although you can do this without it using the command line). But for mobile systems, such solutions, unfortunately, are not provided.