Surely it has happened to many that while we surf the Internet, we try to connect to some site and we find that the browser shows us the message Resolving host and fails to load it. Browsers use a DNS system to translate the name of the site to which we want to go with the IP address where it is hosted and thus show us the corresponding site, however, this is somewhat transparent for users.
Of course, neither computers nor browsers can have information on all the matches between a domain name and IP address, hence a request is requested from a DNS server every time we want to go to a site and it will be the one that returns the answer. For the most frequented, if a table is kept with these mappings so that the next times the access is faster and it is what is known as DNS cache.
Fix: cannot resolve hostname
If the request takes longer than normal, then that is when we come across the famous Resolving host error. A problem that can have different causes and therefore can be solved in different ways. The first thing we can check is if changing to a different DNS service the problem is solved. In most cases, we use the DNS server that of our Internet provider, but if on some occasion it does not work, we can try to change it.
What to do when a DNS server does not respond?
This can be done from the properties of the Internet Protocol in the Windows configuration as you can see in this same link, where you can also see the best DNS servers for this year 2016 so you can try any of them and see if they solve the problem. You can also try checking the option to obtain the DNS server automatically if you are not familiar with these settings, you can also use a third-party application to help you in this task, such as DNS Jumper.
If changing the DNS server the error Resolving host everything is solved, however, if the problem continues, we must proceed with the deletion of the DNS cache, both the one saved by the system and the browser itself. It is very likely that we are trying to access a site that we visit frequently, so it will have been saved in the DNS cache, and yet its IP address has changed.
Therefore, when trying to identify the domain with the IP, we will be trying to connect to the old address and hence we cannot. In order for a new request to be made to the DNS server and return the new one, we must clean the DNS cache of our computer and the browser. From this same link, we show the steps to follow to delete this information both in Windows and Linux and in Chrome and Firefox browsers.
You may like also to read http://www.hostingcultura.com/