Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm frequently - roughly 20% of requests - seeing the following error when opening URLs for the first time:

Error 137 (net::ERR_NAME_RESOLUTION_FAILED): Unknown error.

When I refresh the request, the URL opens correctly.

This only seems to be an issue in Chrome (ie, resolving URLs seems fine in other browsers). I'm using version 24.0.1312.57 m on Windows 7 64-bit.

Does anybody know the root cause of this problem and/ or how I might go about fixing it?

share|improve this question
many solutions can found here – Akam Feb 9 '13 at 20:56
If you try the same site shortly after, does it respond? That is a symptom of a slow DNS resolver, that one should build up a cache of site names over time, so unless you are hitting always different sites this can happen only if that one is rebooted too often. What is your network setup? – vonbrand Feb 10 '13 at 1:05
Yes, if I refresh the site, it usually responds. The network setup is just a home ADSL wireless router using DHCP. It seems unusual in that only Chrome is affected. – James Feb 14 '13 at 17:16

Possibly an issue with one of your local DNS servers - you could try manually setting your Primary DNS Server to and your Secondary to as long as you don't need DNS for an Active Directory scenario. You might find that your router picks up you ISPs DNS server - try manually setting the DNS server to override you ISP's settings to elimnate that as a cause.

If you have an AD setup with a local DNS Server (or two) then look to set your forwarders to and - it's also possible/probable that one of your local DNSes is slow at responding.

Best of luck.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .