NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Getting DNS_PROBE_POSSIBLE error on R8000
In about the last month and a half, I have started noticing two things: * pings spike every 5 minutes, from about 8-9ms, to over 1000ms, for 5-10 seconds (this messes up Remote Desktop) * DNS_PR...
I am also experiencing the same issue, I will get the "DNS_PROBE_FINISHED_NXDOMAIN" error over and over again intermittently. I have never experienced dns issues until these recent firmware updates: 1.0.4.74, and the most recent version 1.0.4.76. Sometimes the website will never load causing some chaos with my online college classes.
I will roll back to firmware 1.0.4.68 and see if that helps. My only concern are these vulnerabilities that have been recently exposed on older firmware. This is the whole reason I updated in the first place. See this article for an example of what made me update….
https://www.pcmag.com/news/thanks-to-disney-11-netgear-routers-need-to-be-patched-immediately
Is there a way to get this info directly to the dev team? This is a huge issue that needs to be fixed immediately. I know I am not the only person experiencing these issues, other forum users have expressed their concerns as well. From a security standpoint we can’t update our routers to old much more vulnerable software versions. This is completely unacceptable.
Note: Facebook and Instagram are both down right now due to other DNS issues?? What is going on?
Another vote for the firmware being the problem causing the DNS resolve errors. Switch to different DNS servers didn't work. A factory reset didn't work. I rolled back from 76 to 68 and the problems went away.
- The only other possible alternative to rolling back the firmware would be to set up and alternate dns server on the computers you use. Setting the alternative dns server to Google DNS servers seemed to get rid of the problem for me. Kinda weird.
- Or using an alternative firmware like fresh tomato. As other users have suggested. Changing the alternate dns server to your default gateway and Google DNS servers seemed to get rid of the problem for me.
Tomato on works on certain models. It does not work on mine. Changing DNS servers on 40 or more clients is not a strategy. Most dont even have a way to change the DNS.
