NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Error DNS_PROBE_FINISHED_NXDOMAIN after update to V1.0.1.70_1.0.44 of firmware
Hi all, Ever since I have updated my AC1750 R6400 router every other site I try to open gives a DNS_PROBE_FINISHED_NXDOMAIN error. If I refresh (F5), the website in question usually opens. It's a bi...
So I downgraded from V1.0.1.70_1.0.44 to (my prevous) version, V1.0.1.44_1.0.31, and everything is hunky dory again. Except, of course that I now miss security updates.
What I find odd, though, is that the router update check now proposes to update to V1.0.1.62_1.0.41. Is that because V1.0.1.70 really has a sort of beta status?
What I wonder with these Netgear devices is this: You're entitled to technical support for a few months after purchasing them, so how on earth will Netgear ever know that subsequent firmware updates contain bugs? I don't get the impression they read these forums.
just an FYI - I just reinstalled my AC1750 (got rid of my Mediacom modem that I got when I moved). I immediately updated to the latest firmware, and I too was getting a million DNS_PROBE error messages.
I also downgraded to the previous firmware, and the problem has totally gone away. Everything is working great now.
fram45trim wrote:
....when I went back to enable and read the process of doing so in the manual, it occured to me that I never reran the setup wizard after changing data suppliers earlier in the year.
You did well to make that move. Well done. A lot of people don't.
Changing ISP is just one event that needs a reset of the router. Your experience suggests that running the wizard achieves the same thing as a reset.
The old service, or an old modem, will create various settings on your router. Change the stuff in front of it, and you need to wipe out those settings and create new ones for the new network.
Glad to hear it worked for you!
Thank you for the suggestion. I had not enabled before, but when I went back to enable and read the process of doing so in the manual, it occured to me that I never reran the setup wizard after changing data suppliers earlier in the year. I reran the wizard and at least for the time being the problem seems to be resolved. After testing I also enabled IPv6 in the auto config mode. Thanks again
Did you try enabling IPv6?
I have the same problem, upgraded to latest firmware yesterday constantly need to refresh page to eliminate "page cannot be found error." Using VPN resolves the issue. Considering going back to previous firmware version, but not sure how to find.
Thanks for your reactions. At least we know we're not alone with this problem. Also personally I'm now sure this has nothing to do with my setup (double NAT), which works without flaws with the older firmware.
However, reverting firmware is not an ideal solution in the end. From hrabcakm I understand that for the R6400 FW 1.0.1.74 (the latest firmware at the time of writing this) still gives problems. So that is at least half a year of Netgear not doing anything about faulty firmware.
I know this is a user community, but I feel it's a disgrace that Netgear cripples their devices by their sloppy firmware updates. Considering the kind of feedback I had to give Netgear in the past (even when my device was still under warranty), I'm not all impressed by the competence of the developers at Netgear and certainly underwhelmed by customer service. I don't think I will buy another device from them anytime soon, even though the hardware is better than that of some of their competitors.
(For those who are interested in what I mean by sloppy coding -apart from rendering the device useless with the past few pieces of firmware - here is an example with regard to port forwarding, where port numbers had to be unique:
Hi,
Same Here. I have following two routers with exactly same issue, 2 differents ISPs.
R6400 FW 1.0.1.74 - Long term issue, present also in previous versions of Firmware
R8000 FW 1.0.4.76 - Same issue, occurs in last 2 Firmware versions.
Hope fix will come soon.
Regards,
M.
It turns out this is a known issue that is affecting many models. For my router R8000-V1.0.4.68_10.1.75 dated 01/08/2021 is the last known firmware that doesn't have this issue. Downgrading fixed it for me.
I have R8000. I recently upgraded firmware that was several years old and have this same issue. I'll reset to factory and try reverting firmware back a few revisions at a time and see if it fixes and which revision started this behavior.
The R6300v2 Firmware Version 1.0.4.52 has the same DNS_PROBE issue. I did not try the 1.0.4.50 level. I went back to my previous Firmware Version V1.0.4.46_10.0.93 and the issue went away. Hopefully Netgear will fix this huge issue in their later firmware levels.
