Unfortunately, sometimes when trying to access a site or even when connecting to the Internet, many users see an error that indicates that the DNS server address could not be converted. What to do in such a situation, not every user knows. But, as it turns out, there is no particular reason for concern, since the failure is eliminated quite simply.
Why can’t I resolve the server’s DNS address?
As you know, DNS servers are a means of interpreting the addresses of Internet resources from a numerical expression to a symbolic one, in which the addresses can use letters, numbers, and special characters.
So what is the reason that sometimes the system fails to resolve the DNS server address? As a rule, this may be influenced by viruses, removal of an anti-virus product (often this is observed with Avast), a “rally” of network settings or incorrectly set parameters. Let's look at a few typical situations with possible troubleshooting methods.
Error "Unable to resolve server DNS address": what to do first?
First of all, you should check your computer for viruses. You never know, maybe the reason is really just that. But you need to use some third-party product for this, and not a regular scanner.
But even if no viruses are found, the system can still display a message stating that the DNS server address cannot be resolved. So, the problem is just in the network settings. Therefore, initially you need to check whether such a message is issued only when accessing a specific site or in general to all pages when trying to open them. If possible, it is better to check access from several devices, say, from a desktop computer, laptop and smartphone. If only one site does not respond, it is possible that technical work is simply being carried out on it. If access is blocked for all resources, the problem may be caused by the provider. But subject to the possibility of access from any one device, the reason that the system cannot convert the address of the DNS server should be searched for exactly the installed network parameters.
Checking DNS Client Status
On a desktop computer or laptop, you should first check the status of the DNS client.
To do this, use the services section, which can be entered through computer administration, but it is easier to immediately enter the services.msc command in the Run console Win + R). Here you need to find the appropriate line and look at the installed startup type. The parameter should correspond to automatic start. If the value is different, call the properties menu and change it.
Control settings of the protocol used
If this solution does not work, you need to use the network settings, in particular, the default protocol (usually IPv4).
We find it in the section for changing the settings of the network adapter, click the properties button and check what is set in the fields of the preferred and alternative DNS server. Perhaps, as often happens, automatic retrieval of parameters is set.
You can try to change them to the values offered by the Google Public DNS service. Here in one line you should set four eights, and in the other - two eights and two fours. In principle, what combination will be used for each type of server does not play a special role.
Clearing the DNS cache and restoring settings
Finally, if the error message stating that it is still not possible to resolve the DNS server address appears again, you can simply clear the DNS cache or even reset the parameters.
For the cache, the command line is used, launched with admin rights, in which ipconfig / flushdns is written. You can, of course, add configuration re-registration commands, but in most cases normal cleaning is enough.
In principle, if you are too lazy to do such things, you can download and install the special Microsoft Fix It! Application on your computer! (By the way, it was designed specifically to eliminate errors in connecting to the Internet). It is enough to simply activate the utility and wait for the scanning process to finish and eliminate the failures (the processes proceed fully automatically without user intervention).
Instead of an afterword
In general, the proposed solutions can eliminate a lot of problems regarding DNS settings. They are equally well applicable not only to the error described above, which has the 105th code, but also to some other failures, when problems of this nature are called as the main reason for the lack of communication or access to resources. But if you approach the elimination of the failure from a practical point of view, many users who are not particularly versed in network settings can be advised to use the "native" program from Microsoft, especially since no one knows the Windows system better than themselves. But in principle, if there is at least some idea of the system settings, it is better to turn to solutions without using an automatic fixer.