Solved

How do I Fix Google Chrome "Error Code: DNS_PROBE_Finished_NXDOMAIN" Issue?

Posted on 2014-04-23
3
64,722 Views
1 Endorsement
Last Modified: 2015-07-14
I have a small office network with 2 desktops and 3 laptops connected to a D-Link DIR-655 X-treme N Gigabit Wireless router.  The D-Link is connected to a Comcast modem.  Users on this network have intermittent problems with Google Chrome when they try to access certain websites.  They receive the attached error message.

It definitely doesn't seem to be an issue with the network being configured incorrectly, because ALL users can access the same websites that are sometimes blocked by Google Chrome with both Firefox and Internet Explorer

Can anyone give me any insight into what may be causing this and what must be done to fix it.  Keep in mind, this Error only happens in Google Chrome, Firefox and Internet Explorer are working perfectly.

Another thing to consider is that I don't have this problem with Chrome when I use one of the laptops at home, it only happens at the office.  I know that makes it seem that it would be a network configuration issue, but the other browsers work fine at the office.  This is a very strange problem.

Any assistance would be greatly appreciated.
Chrome-DNS-Error-Screenshot.jpg
1
Comment
Question by:ghostfrog
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 19

Expert Comment

by:*** Hopeleonie ***
ID: 40019340
Hi

Did you try to flush your DNS?
How to do:
http://help.ea.com/en/article/how-to-flush-dns-cache-for-windows/

Also try to restart your Modem / Router.

Also check this link:
https://support.google.com/chrome/answer/117805?hl=en-GB
0
 
LVL 82

Accepted Solution

by:
David Johnson, CD, MVP earned 500 total points
ID: 40019431
change the dns settings in your adapter and/or the router to use another dns provider i.e. 8.8.8.8 / 8.8.4.4 google dns .  A lot of people are getting this error the timeout must be set by default as being too low (you can't change it) .. A last gasp solution is to uninstall and then reinstall google chrome which has solved it for when changing the dns provider didn't help.
0
 

Expert Comment

by:techski
ID: 40882040
For anyone else having the same issue, i have found very good steps at http://appuals.com/best-fix-steps-fix-dns_probe_finished_nxdomain/
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you using email marketing software? If not, you're missing out on effortless marketing and the reaching of desired conversion rates through email marketing software.
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

622 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question