DNS Lookup Failed Google Chrome

Toggle sidebar Toggle sidebar
D

DominusAnulorum

Honorable
Jan 2, 2014
2
0
10,510
I recently moved into a new apartment and got a router for the first time ever. I have a desktop and laptop. About a week ago Google chrome on my laptop stopped connecting to the internet. Every other browser worked perfectly fine, but chrome give me DNS_PROBE_FINISHED_NO_INTERNET whenever I try and use it. I re-installed and reset every single internet setting on my laptop, but nothing has worked. I thought it might be maleware, but the problem then spread to my desktop today as well and I am at a complete loss for an explanation. It isn't a firewall issue, I reset the winsock connection, I renewed and reset my ip connection, and I disabled add-ons. Chrome still throws up the same error message. None of my roommates are having issues with chrome except for me. Help would be greatly appreciated!

edit: can anyone shed light on my problem? no responses in a week is rather impressive
 
Sort by date Sort by votes
S

scoldilocks

Reputable
Sep 11, 2014
3
0
4,510


Not sure, but I am suddenly having a similar problem. My issue is limited to using Chrome and Google sites/products, however. Gmail, Google search, Drive, all very slow to load. I also occasionally get a DNS error of some kind and cannot access anything. The hanging/slow-loading in Chrome I thought was resolved after I installed a new modem (Motorola Surfboard SB6141). Everything in Chrome and elsewhere became lightning fast and no issues. Then I updated my router's firmware, and the DNS problem started, though it is intermittent. But the slow-load and hanging on Google sites using Chrome returned. I have zero problems with this in Firefox or IE.

 
Upvote 0 Downvote
I

imtiaj

Reputable
May 1, 2015
5
0
4,510
This problem occurs when the automatically obtained DNS server stops responding. You can solve the problem by changing the DNS server addresses to either Open DNS or Google DNS. Check this out for a complete tutorial - http://www.pcappspot.com/dns-lookup-failed-fixed/
 
Upvote 0 Downvote
S

sudhir_2

Reputable
Aug 26, 2015
1
0
4,510


 
Upvote 0 Downvote
C

Charlie247

Reputable
Aug 27, 2015
1
0
4,510
I have had this on many systems using Chrome and I share the pain with trying to resolve the issue as system wise all will look OK.

To recap my experience:
Any ping to the domain or NSlookup for the failed domain on all the locally used DNS servers would work fine.
Trace routes would all be fine.
Any other browser can access the failed domain.

Many forums suggested flush the DNS using ipconfig /flushdns or reset the winsock catalog. Sometimes the flush DNS would do a temporary fix but shortly after it would fail again or on next reboot it would fail.

After a lot of frustration what worked for me was to disable "Prefetch resources to load pages more quickly"
This can be found in Settings >> Show advanced settings >> Privacy

It looks like Chrome tries to get all the DNS information on startup for its regularly visited sites and fails but keeps the Failed information instead of actually going to query the DNS information or refresh.
 
Upvote 1 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom