DNS_PROBE_FINISHED_NXDOMAIN on Google App Engine website

Asked 9/6, 2015 at 8:40 Answered 9/7 at 9:15

For unknown reasons my website on Google App Engine is suddenly not loading anymore on multiple devices and in different browsers. It gives a DNS_PROBE_FINISHED_NXDOMAIN error. I tried restarting the DNS service, changing DNS to Google's, and restarting devices. Nothing helped so far. All other websites load without issues. What could be causing this?

Walking answered 9/6, 2015 at 8:40 Comment(9)

downforeveryoneorjustme.com – Glaciate 9/6, 2015 at 9:5

Thx. Down for everyone according to this website. So I have to check my domain settings? – Walking 9/6, 2015 at 9:8

Oh, just wanted to login to WhoIs domain registration and I get the same error. So guess those guys are having an issue... – Walking 9/6, 2015 at 9:9

I guess so. My GAE site (on a custom domain) is running – Glaciate 9/6, 2015 at 9:9

Yes, the .appspot.com version of my page works without problems. – Walking 9/6, 2015 at 9:10

Voted to close, as it's just a specific issue for you, not a question that can be answered. Good luck getting it sorted. – Glaciate 9/6, 2015 at 9:10

Ok sure. Thanks. Should I close this myself by adding an answer or is that an admin thing? – Walking 9/6, 2015 at 9:11

you can just delete it or adding your own answer is also acceptable :) – Glaciate 9/6, 2015 at 9:13

downforeveryoneorjustme.com return : It's not just you! google.com is down. _ This website is not working properly _ @PaulCollingwood – Resee 7/2, 2022 at 8:0

Seems like there are some issues at my domain provider. Their website is giving the same error.

Walking answered 9/6, 2015 at 9:14 Comment(0)

I've spent weeks fighting with this problem on 2 different unrelated computers, even unable to ping Yahoo.com and having variety of connectivity issues in web browsers, including "DNS_PROBE_FINISHED_NXDOMAIN" and "ERR_NAME_NOT_RESOLVED". I've tried various ipconfig commands, restarting DNS client service, "netsh winsock reset", and other solutions found on the internet.

Finally I realized the only common thing on both my computers was Malwarebytes. After closing/exiting Malwarebytes the problem was solved. I am now able to ping and access every website. The solution, again, at least in my case: close Malwarebytes

I just contacted Malwarebytes support but in the meantime wanted to provide the solution here.

Probably answered 13/6, 2016 at 16:10 Comment(0)

Run following command from cmd

ipconfig /release

ipconfig /all

ipconfig /flushdns

ipconfig /renew

netsh int ip set dns

netsh winsock reset ###( Need to run in administrator mode)

If not successful then

Restart your PC

Incontrollable answered 19/5, 2017 at 6:39 Comment(0)

In my case, I deployed my app in AWS Amplify and got my domain from GoDaddy. When this error was coming and my site was crashing, all I did was waited for 48 hours for the nameservers to transfer from GoDaddy to AWS. The process is called 'propagation time' and yes, its silly because who wants to wait for 48 hours in a world where nobody has patience.

GoDaddy is slow. if you dont want to deal with this problem, then I would suggest to get your domain from AWS route 53 only, instead of buying them from other third party companies like GoDaddy.

Cockadoodledoo answered 9/7 at 9:15 Comment(0)

Recommended topics

Hot tags