Is this error message the website or local computer?

[Sausages]

I was told my site is returned an error:
This webpage is not available
DNS_PROBE_FINISHED_NXDOMAIN


When I check or ask other people to check it loads ok. Is this a local issue, or an issue with my website? It's difficult to find the answer online.

Thanks

[robertmedl]

Am getting same error when trying to get to bettingpartners.com from Loveland, Ohio.

This webpage is not available


DNS_PROBE_FINISHED_NXDOMAIN
ReloadHide details
The server at www.bettingpartners.com can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.

[TheGooner]

IF you are getting the errors in Google Chrome - then it's probably an issue directly related as to how Chrome gets it's routing information.
It's NOT a problem with the website or servers - it is a problem specific to Chrome

There is a potential (temporary) fix to get it working again.

1/ Right click on the Windows Start (lower left hand side) and choose "Command Prompt"
This will create a small DOS command box.

2/ Inside the box type IPCONFIG /FLUSHDNS
This drops previous routing information - and makes chrome look for a new path.

Try to access the site now chrome and it should work fine (if it is this problem).
Note this is not a permanent fix - if the routing path changes in future - you'll need to do it again.

The permanent solution is simply to use Firefox or Microsoft Edge to access the net instead.

[universal4]

NXDOMAIN is the answer a dns server will return when a dns server is queried that does NOT provide recursive lookups. (this is also a behavior that can be seen when the recursive server queried has had their cache poisoned after a poisoning attack)

Like TheGooner suggested, a dns flush might fix the issue, or depending on your isp it could be the dns server they are using as default can not query the specific domain for whatever reason.

If the problem persists and it is a site you need to reach often, you could change your dns on your local computer or on the router.

If the dns server that is used by the isp, or more specifically your router/computer, can not reach any specific website, changing browsers will most likely not help since browsers will use the dns assigned to the connection.

Rick
Universal4

[TheGooner]

If the dns server that is used by the isp, or more specifically your router/computer, can not reach any specific website, changing browsers will most likely not help since browsers will use the dns assigned to the connection.

Agreed if it IS actually a DNS problem - then getting a fresh route map won't do anything - you still won't be able to get there.

But - when it involves the Chrome browser then 99% of the time then error is directly related to Chromes DNS handling and flushing the local DNS map on your computer will fix the problem. For example, Robert cannot get to BettingPartners above and it has not been out for me for months.

The easiest way to see if it's Chrome only is to have Firefox / MS Edge also on your machine and you can do a quick test.

If Robert sees this - I'd love him to try :
a/ Use Chrome again to get to Betting Partners. Does it fail? YES/NO
b/ Use Firefox to get to Betting Partners. Does it fail? YES / NO
c/ Try Chrome again to get to Betting Partners. Does it fail? YES/NO
d/ Flush the DNS
e/ Try Chrome again to get to Betting Partners. Does it fail? YES/NO

I'd expect Chrome to fail, Firefox to work, Chrome to still fail, the flush to be done, Chrome finally works again.

I am amazed that this Chrome only issue persists - and that they continue with a method that has problems when routes change (a server in the path breaks). I think it must have something to do with tracking data that Chrome is storing and passing back to Google but it's only my opinion / conspiracy theory.

[universal4]

True Paul,

Any problem that Chrome has that IE/Edge and Firefox can do better shows just another Chrome flaw.... (sorry couldn't resist)

My guess is this is the same root cause that cases the public recursive google dns servers get the wrong answer often also. Or maybe they always query their own servers instead of going to root/authoritative and only check for the real path after the flush. ??

Rick
Universal4

[robertmedl]

Yes, I was using Chrome when I encountered this error.

The issue corrected itself w/o me having to follow the guidance that you have provided. I'll be sure to reference your guidance if the issue occurs in the future.

Thanks!