Can not convert the DNS server address: how to fix the error with the simplest methods?

Unfortunately, sometimes when you try to access a particular site or even when you are connected to the Internet, many users see an error in the message stating that the DNS server address can not be resolved. What to do in this situation, not every user knows. But, as it turns out, there are no special reasons for concern, since the malfunction is eliminated quite simply.

Why can not I convert the server's DNS address?

As you know, DNS servers are means for interpreting Internet resource addresses from a numerical expression to a symbolic one, in which letters, numbers, and special characters can be used in addresses.

So what's the reason that sometimes the system can not convert the DNS server address? Typically, this may be the impact of viruses, the removal of an antivirus product (often such is observed with Avast), "gathering" of network settings or incorrectly set parameters. Let's consider some typical situations with possible methods of troubleshooting.

"Can not convert DNS server address" error: what should I do first?

First of all, you should check your computer for viruses. Little, perhaps, the reason is really in this. But to use this, you need some third-party product, not a full-time scanner.

But even if no viruses are found, the system can still issue a message stating that the DNS server address can not be resolved. So, the problem is just in the network settings. Therefore, you first need to check whether this message is issued only when you access a specific site or even all pages when you try 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 answer, it is possible that technical work is simply carried out on it. If access is blocked for all resources, the problem may have a cause on the part of the provider. But if you can access from a single device, the reason that the system can not convert the DNS server address is to look for exactly the network settings.

Checking the status of the DNS client

On a desktop or laptop computer, you should first check the status of the DNS client.

To do this, you use the services section, which you can enter through computer administration, but it's easier to enter the services.msc command in the Win + R console at the console). Here you need to find the appropriate line and look at the set start type. The parameter must match the automatic start. If the value is different, call the property menu and change it.

Monitoring the settings of the protocol used

If this solution does not work, you need to use network settings, in particular, the default protocol (usually IPv4).

We find it in the section of changing the network adapter settings, we click the properties button and check that it is installed in the fields of the preferred and alternative DNS-servers. It is possible, as it often happens, to automatically obtain parameters.

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, which combination will be used for each type of server, does not play a special role.

Clear DNS cache and restore settings

Finally, if the error message stating that you still can not convert the DNS server address appears again, you can simply clear the DNS cache or even reset the parameters.

For the cache, a command line is run, running with admin rights, in which ipconfig / flushdns is set. You can, of course, add more commands to re-register the configuration, but in most cases there will be enough cleanup.

In principle, if you are lazy with such things, you can download and install a special Microsoft Fix It application on your computer! (By the way, it was designed to eliminate errors in connecting to the Internet). It's enough just to activate the utility and wait for the scanning process to finish and fix the failures (the processes run completely automatically without user intervention).

Instead of an afterword

In general, the proposed solutions can eliminate a lot of problems related to DNS settings. They are equally 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 named as the main reason for the lack of communication or access to resources. But if you approach the elimination of a malfunction 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 at least some notions about the system settings are still there, it is better to turn to solutions without using an automatic fixture.