Chrome’s “Resolving Host” Problem Solved

Well, solved for me anyway.  Sometime a few hours after it was released, Firefox stopped becoming my regular browser, and Chrome *did*.  I know — I was kind of amazed myself, in spite of all the plugins I’ve been missing.  At any rate, one thing I’ve begun noticing has been getting worse: its seeming inability to “resolve the host”.

This would lead to the browser essentially “hanging” and then timing out while it was waiting to fetch web pages.  For a browser that I’ve been relying on mostly … well, to browse … this was becoming problematic.

Turns out there are a few easy solutions for this that you can try:

1. delete your cache

2. delete your browsing history

3. delete your download history

4. disable “DNS pre-fetching”

Personally, I skipped right down to #4, and once DNS pre-fetching *was* disabled, Chrome was as zippy as ever.  As always use the above tips at your own risk if you feel like trying them out.  

via: Google Groups

19 Comments

  1. Posted September 22, 2008 at 10:20 am | Permalink

    Been having the same problem with Chrome lately so I also tried the same trick and it worked! Thanks :D

  2. EdB
    Posted January 15, 2009 at 5:15 pm | Permalink

    Same for me as jhay: tried it, seemed to work right away. Thanks!

  3. StevenMc
    Posted February 1, 2009 at 1:37 pm | Permalink

    I found the solution to be a little more complicated.

    Step 1:
    In Chrome, click the wrench icon, select “Options” then “Under the hood”. Hit the button at the bottom that says “Reset to defaults”.

    Step 2:
    On the same screen, make sure “Use DNS pre-fetching” is un-checked.

    Step 3:
    On the same screen, scroll down and press the button that says “Change proxy settings”.

    Step 4:
    This assumes you are on broadband (with a pen and paper, write down your current settings so you can back them up if things go wrong). Click on “Lan Settings”. Make sure “Automatically Detect Settings” is un-checked. Click “Ok”.

    Step 5:
    Go to the Window XP/Vista Control Panel (Start, Settings, Control Panel). Load up the “Network Connections”.

    Step 6:
    You will now see a list of the network cards and bridges on your computer. Only one of these is used by your computer to connect to the internet. For example, if you are using wireless internet you will only be using the wireless connection. Right click on each other connection and select “disable”. You should only have one enabled connection.

    Step 7:
    Restart your machine. Turn it off and on again. This is a very important step.

    Step 8:
    Google Chrome will now be working fully. If not, then clear your history and cache and restart the browser.

    This worked for me. It took me about 2 or 3 minutes in all, and made Chrome perfectly fast. No more “resolving host”.

  4. ekaplan
    Posted April 16, 2009 at 7:59 am | Permalink

    The 9/17/2008 post suggested works for me (deleting history, set to default, uncheck DNS pre-fetching), then log out of Chrome and back in…but I have to do this 5-10 times per day.

    This isn’t a solution, something is wrong.

  5. ekaplan
    Posted April 17, 2009 at 10:00 am | Permalink

    Update for anyone: I was using the BETA version of Google Chrome. I uninstalled it and went back to the Released version and the need to apply the 9/17/2008 solution 5-10 tiems per day seems to have gone away.

  6. Posted May 11, 2009 at 6:51 am | Permalink

    Thanks for the update ekaplan … I recently installed Chrome again on a new PC, and had the same problem until I remembered this old post.

    I still had to disable DNS fetching, however, as I had ongoing “host resolving issues”, but once I did it was lickety split ;)

    cheers
    t @ dji

  7. Anonymous
    Posted May 19, 2009 at 11:13 pm | Permalink

    Me too. Amazingly I think it did very well help. I have searched for two days trying to figure this out. Thanks so much for the tips. Wink! Wink!

  8. Steven
    Posted May 23, 2009 at 5:59 pm | Permalink

    Well done! This worked for me!

    Thanks!

  9. john
    Posted May 28, 2009 at 5:49 pm | Permalink

    this resolving host thing just started happening to me today after i downloaded something. so i think it was caused by a virus in my case, slowed everything down, and i found the virus with adaware straight away too (at least i hope i got it).
    i tried the steps above and they seem to have worked, will have to see.. but i think i still have some other problems because of the virus.

  10. tunder
    Posted June 5, 2009 at 2:06 am | Permalink

    It works for some time, but in 10-15 min I have the same problem… It’s not the final solution…

  11. tunder
    Posted June 5, 2009 at 2:09 am | Permalink

    It works for some time, but in 10-15 min I have the same problem… It’s not the final solution…
    By the way. In my case I have this problem only if I have wireless internet. On the cable it works fine…
    Could it be some kind of problem with my router?

  12. Ashish
    Posted June 5, 2009 at 6:04 am | Permalink

    It worked perfectly for me. Kudos !!

    Thank ew ~

  13. ekaplan
    Posted June 7, 2009 at 10:26 am | Permalink

    “Resolving Host” problem came back again to me today, and the steps above didn’t resolve it–but then completely uninstalling Google Chrome (but saving your preferences) and reinstalling it did resolve it–at least until it reappears again.

  14. Ryan
    Posted June 18, 2009 at 1:00 am | Permalink

    Thank you! I want to like this browser but the resolving host dealio was driving me nuts.

    The DNS tweak was the solution.

  15. mikeeotis
    Posted July 10, 2009 at 1:28 pm | Permalink

    The DNS tweek works great for me :)

  16. Yannis
    Posted November 29, 2009 at 5:55 pm | Permalink

    #4 did it – you nailed it – thanks

  17. nan d
    Posted November 30, 2009 at 1:27 pm | Permalink

    Awesome! Was driving me crazy

  18. Kyle
    Posted December 4, 2009 at 8:11 pm | Permalink

    I was having the problem and couldn’t get any of these solutions to work. I then tried reinstalling Zone alarm and that seemed to resolve it.

  19. manoj
    Posted December 26, 2009 at 11:21 pm | Permalink

    yeah! its working….

Post a Comment

Your email is never published nor shared.

Powered by WP Hashcash