Turn Off DNS Prefetching in Google Chrome to Fix Resolving Host and Cannot Load Page Error
Google Chrome has a built-in DNS pre-fetching mechanism which intends to improve page load performance. However, the feature has known to work to the contrary effects. With DNS prefetching enabled, users of Google Chrome may experience prolong or extended period of web browsing resolving the DNS name, with the following text displayed in status bar:
Resolving host…
Besides, Google Chrome also may not, cannot or unable to load some web pages, leaving the web pages in blank and white without any text, or the following error message is displayed:
This webpage is not available.
The webpage at http://www.askvg.com/how-to-disable-window-borders-blur-in-windows-7/ might be temporarily down or it may have moved permanently to a new web address.
Here are some suggestions:
Reload this web page later.
Clicking on the “more information on this error” will display the following technical details:
Below is the original error message
Error 105 (net::ERR_NAME_NOT_RESOLVED): The server could not be found.
The error normally goes away after a refresh button click or F5 button click. However, some users may need to close Google Chrome, run Internet Explorer browser and then restart Google Chrome web browser to fix and resolve the issue.
The problem is caused by unreliable implementation of DNS caching or prefetching in Google Chrome web browser, or buggy coding of Google Chrome’s network I/O (input output) stack.
As a result, turning off and disable DNS pre-fetching may actually solve and fix many web page not loading issue in Google Chrome. Here’s how to disable and turn of DNS prefetching in Google Chrome.
- In Google Chrome, click on Tools menu (a little wrench icon), then go to Options.
- Click on the Under the Hood tab.
- Under “Privacy” section, untick the check box for Use DNS pre-fetching to improve page load performance.
- Click on the Close button.
- Refresh to reload the web page.
I have broad band connection in my home.I connected it to desktop and it is working.But when i connected to my laptop it is not working.
Please provide solution….
mi computadora tiene windows xp y me genera este error Error 105 (net::ERR_NAME_NOT_RESOLVED): y no se mucho de computadoras me podrian ayudar…..!!
Edit Fixing DNS ERROR 105 in three steps.
1)Change Wireless adapter settings from network connections, go to properties>internet protocol version 4>again properties> change to use following dns server.preferred dns to 208.67.222.222 and alternate dns as 208.67.222.220 and click validate setting on exit and ok.
2) if you are using windows7, disableMS WINDOWS VIRTUAL WIFI MINI PORT bu running below 2 commands in” RUN” (windows key+r) shortcut. one after another.
1) netsh wlan stop hostednetwork
2) netsh wlan set hostednetwork mode=disallow
and after running above commands close RUN and go to network connections and DISABLE Microsoft virtual wifi miniport by right click and disable.
3)If you are using google chrome go to OPTIONS> UNDER THE BONNET>CHANGE PROXY SETTINGS>CONNECTIONS>LAN AREA SETTINGS> Tick use a proxy server for lan and clock ok.
(if you are using some other browsers, check for similar option and change settings as above)
additional solutions
a) check for your anti virus firewall to minimum(if it is problem only)
b)reset modem(only for advanced users who can once again set up connection settings)
c)ping to router or a site to know the problem.
hope this helps to some one. bye
Truly That Was Easy, And Fantastic Move!.
Really Thanks!..
Thanks Alot
This is very useful.
I have noticed that chrome hangs since i have changed my internet service provider. turning off dns prefeching solves the problem.
Thanks, amigo. You solved my biggest problem with Chrome. I'd switched back to IE and Konqueror.
This solution worked. Many thanks.
I have slow DNS problem with IE8 and Chrome on XP. That DNS prefetch uncheck didn't do it for me. I think it's about IPv6 vs IPv4 conflict. In FF I disabled the network DNS IPv6 in about:config and it was back in business. Can't do it in IE or Chrome. My problem appeared when my IP provider changed my modem with Huawei HG655. Didn't find so far anything helpful for that.
Hey thanks so much! Worked like magic
I'm having problems as well. This did not solve it.
Only certain visited pages become "not found" across all browsers. I believe it has to do with Chrome. Using just firefox, after restarting the airport, works fine. But if I use Chrome, then use Firefox, visited pages go down after a few moments.
I have the same problem… I cant open only most visited pages by me… Facebook, Google an Youtube… Rest of them works fine… I have scaned for viruses and malware software… I have found nothing that can resolve this isue… If someone could help me I would be thankfull… I ve also tried several solutions including this one… nothing works… its driving me crazy… tnx for help!
Hi I have a problem I've had google chrome before and it works very well but any moment now when I woke up this morning it worked no longer just stopped loading pages. I tried to do so that it stays there but nope did not help. Can someone be kind enough to write to my email and help me?
[...] DNS pre-fetching also helps to solve Chrome cannot load and open web pages [...]
Thanks for the info. I am just curious as of today's current version if this is still a problem? Sometime last year I finally tried out chrome and was disappointed. I uninstalled it and started using firefox and ie again. Both have been going slow javascript wise (of course ff is faster though). So I decided to give chrome another try and it has improved so much. I am impressed. I haven't had this sort of problem and am curious if others continue to have this problem with the most current version.
Thank you! This actually solved my problem.
[...] the majority of them may not ever be clicked by users who view these pages. In fact, it is said in this blog entry that DNS prefetching can lead to the browser spending much time resolving hostnames. It is also said in that entry that incorrect implementation of DNS caching or prefetching or other [...]