Sometimes when I want to visit random site I get "The server at www.something.here can't be found, because the DNS lookup failed" which looks pretty standard. When I go to "chrome://net-internals/#dns" settings, I get "error: -105 (ERR_NAME_NOT_RESOLVED)" error.

Suprisingly - when I go to this same exact site using IE it works pretty solid. In my opinion it's default dns timeout span, which is too short (?) and I can't find a way to make it longer but maybe I am missing something?

Windows 8.1 (with all hotfixes)
Chrome stable version (tried beta, nothing changed)
flushing windows DNS (which doesn't help probably because Chrome has it's own DNS cache.

What could be wrong? Thanks in advance!

  • 1
    Who are using for you DNS servers? ISP, google, OpenDNS? Have you tried switching servers to see if it helps? Nov 30, 2013 at 14:31
  • Got and ad Preferred and alternate DNS - can't check it now but as I recall it's opendns + google. Tried to change it but I'm not sure if it helped - problem still exists
    – GoMati
    Nov 30, 2013 at 14:34
  • Here's a relevant thread that recommends not mixing DNS services... forums.opendns.com/comments.php?DiscussionID=12307 Nov 30, 2013 at 15:18
  • I doubt a little that's the case, but I will try it ASAP. Thanks! :)
    – GoMati
    Nov 30, 2013 at 15:25
  • I also doubt it, but when in troubleshooting mode, I start with the basics and start with the simplest configuration. In this case, that would be google OR OpenDNS. Nov 30, 2013 at 15:53

1 Answer 1


You can try flushing Chrome's DNS cache

Flush cache

If that does not work, consider disabling DNS prefetching.

Disable DNS prefetching

More details on Chrome and DNS prefetching.

  • That option is not present on Version 42.0.2311.90 m (Windows 8.1). Has it moved?
    – Mogsdad
    May 13, 2015 at 13:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.