NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Latest update bug: R6400 Firmware DNS issue (V1.0.1.74_1.0.48)
This latest update broke DNS resolving, so it randomly cuts out and doesn't resolve anything. Random web pages will just error out. Connection to generic services won't work at all.
More can be seen here https://www.reddit.com/r/NETGEAR/comments/ozx8l7/netgear_r6400_dns_breaks_after_firmware_v10168/
Please fix.
It's apparent that since the DNS problem arose, subsequent and unrelated updates have made the router(s) even worse. In fact, I think Netgear is imploding as we speak.
“Way to go Disney! I have disabled automatic updates because the last update from Netgear slowed my router down so much. I had to downgrade to a much older version that did not include the armour guard application to get my full isp speed back. I am afraid that this new patch will come with the same application that I had to get rid of that slowed down my router. Maybe it is time for a new wifi 6 router from a different company.”
“the same issue with the 6400v2 downgraded the firmware which helped get more speed but ultimately bought a new router the Rax50 to keep up with the speeds much happier now.”
Source: PCMag comments / Netgear forum
I do however have a solution to my issue; I bought a non-Netgear branded router. Are you looking for a router with stability, performance and industry standard updates that don't break the the product altogether? Look no further.
- Enjoy ultrafast speeds up to the advertised data transfer and WiFi speed rates
- Guaranteed DNS functionality
- Don't include blueprints by Microsoft listing amateur router exploits
Buy anything but Netgear today. Special thanks to olympos1625 for logging in the forum every day and ignoring everyone while having the time to respond to new threads. I hope everyone else gets a working router sometime soon because this is verging on class action territory when the product isn't end of life. Oh, how the mighty fall.
49 Replies
I'll be downgrading instead as this isn't new and I didn't know my router version before I opted to manually upgrade.
I'd like to personally thank Netgear
for breaking products which could spur people into buying a Nigh----- I mean, for providing excellent updates.I too had same DNS problem... it's outrageous that this was not detected before release.
HI NamelessPerson,
Welcome to NETGEAR Community!
Thank you for reaching out. We are sorry to hear about your experience with the router. May we know if you reset the router after updating the firmware to the latest version? If not, please do so and see if you still encounter the same issue. If still you are getting the same issue after resetting the router to factory default after updating the firmware, please DM us the following information:
Name:
Email:
Phone:
Preferred schedule (atleast 2 days ahead)
Timezone:
Device S/N:
Alternatively, if you wish to be contacted via email only then kindly include your preferred email address.
I am looking forward to your response.
Regards,
Oliver
Community Team
I had the exact same problem as NamelessPerson.
And yes, I reset my router and that solved nothing except disrupted the home internet...I ended up reverting back to V1.0.1.68_1.0.43
And with that, the DNS resolving problem was resolved.
Please quickly fix the firmware so I can get whatever security issues were addressed.
Same issue. Breaking DNS in an firmware update is pretty facepalm Netgear. Be better!
Downgrading to V1.0.1.68 and then resetting the router worked for me - someone else said that of V1.0.1.70. I am not going to trial updating again just to encounter the same problem (other people are using the network for important work). Please refer to the other comments in this thread and:
https://www.reddit.com/r/NETGEAR/comments/ozx8l7/netgear_r6400_dns_breaks_after_firmware_v10168/
https://www.reddit.com/r/NETGEAR/comments/p4uu3i/router_r6400v2_keeps_giving_me_page_cannot_be/
This is a firmware issue and we'd appreciate an update as to whether or not you intend on fixing it with a reasonable ETA.
Hi Guys,
Thank you for reaching out. Our Engineers are looking into this issue with the latest firmware and have provided us a beta firmware. Please DM us your registered email address so we can provide you this firmware and see if it fixes your issue.
Regards,
Oliver
Community Team
Hi NamelessPerson,
Thank you for your response. We are sorry again for the inconvenience this has caused you. We have forwarded some users already to our Level 2 Support for further assistance. We will update you as soon as possible.
Regards,
Oliver
Community Team
Oh thank goodness it's not just me. I was going crazy cause I thought it might have been the new Windows update but my router updated at the same time.
I did a reset, tried setting the DNS manually to Google and Cloudflaire and still had the same issue. I was starting to think it was something else.
I finally rolled back my firmware to version V1.0.4.106_10.0.80 and that seems to have fixed my issue.
bouncdchk wrote:
Oh thank goodness it's not just me. I was going crazy cause I thought it might have been the new Windows update but my router updated at the same time.
I did a reset, tried setting the DNS manually to Google and Cloudflaire and still had the same issue. I was starting to think it was something else.
I finally rolled back my firmware to version V1.0.4.106_10.0.80 and that seems to have fixed my issue.
===
I did this on two separate routers and both are back to functioning without the DNS problem. Netgear - Please let me know when the new firmware update is availlable without this DNS problem. I wasted a lot of my time on this problem. Not happy about it!
Would appreciate it if you can advise how you got older firmware versions like this one from the support site? The oldest listed under, "previous versions" is 1.0.2.52 and I can't seem to get to anything older than this...
Rolling back only to 1.0.2.52 sounds like it would not fix this issue....
Same here. R6700v3. Been nothing but trouble this last year. Requiring daily or every other day power cycles. Now with the latest firmware I get DNS issues on all devices.
I am experiencing the same issues discussed in this thread on multiple devices with my R6400 after installing the latest firmware (V1.0.1.74_1.0.48.) Please fix this firmware issue. This is wildly annoying.
I had the same issue. The problem is with Firmware version 1.0.1.74_1.0.0.48. This can be found all over Reddit and this community forum, but it looks like NetGear is not accepting responsibility. They're instead telling people it's a problem with their firewall or with thier internet server providers DNS resolution. I've been using this router for 5 years without any issues until this update.
There are also documented cases of running wireshark to track the dns errors. Many are detected on resolving DNS inside the network (like the router's own IP address), so the Firewall and ISP DNS resolution aren't even in play.
I didn't want to do a factory reset because I have way to many advanced configurations set up in my router to go through setting up again.
I ended up rolling back to a previous version and then ran these commands in an elevated command prompt and it looks like it might have fixed the problems.
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Just make sure to downgrade to V1.0.1.68_1.0.43. The issue is completely resolved by that version. The broken version isn't even available for updating through the firmware anymore, so they know there's an issue with it. Hopefully the next update will fix it, but if it doesn't have V1.0.1.68_1.0.43 handy so you can downgrade again if necessary.
Same issue as everyone else with V1.0.1.74_1.0.48. I haven't downgraded my firmware yet but probably will soon since it seems that Netgear has not acknowledged the problem and it seems like their support staff is going to go in circles reading their scripts on how to disable firewalls and blaming the ISP. Has anyone successfully and painfully gotten Netgear to escalate this issue?
Netgear forum staff don't even know how the Access Control feature works when helping someone troubleshoot; they always default to reset and hope for the best. Why would they be able to communicate being proactive about something like this?
As far as I can tell they are kicking the can down the road because the model will just be replaced by people who have an issue. It absolutely reeks of racketeering if I've ever seen it.
I've run this experiment twice now. After ugrading to 1.0.1.74, DNS errors across all my network. I've downgraded now to V1.0.1.68_1.0.43 and not a problem in the world, everthing is perfect! There's no way this is "something" in my network.
C'mon Netgear... admit the error and fix it!
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.
I want to give a big thanks to all in this thread and others related to this problem. I had the same issue on r6400v1 after it crashed (first time ever) and I decided to upgrade firmware to the latest release - DNS errors ever since. It took me some time to research and finally came across these threads with specific and useful info for this model. Downgraded to 1.0.1.68 and so far so good. I wouldn't have known how far back to downgrade otherwise.
It's been 9 days and I see you're active in new threads. Can you send over that beta firmware please? I sent you my email last week. Personally, keeping up to date with security patches is paramount. It doesn't seem the firmware is going to be released anytime soon.
It's apparent that since the DNS problem arose, subsequent and unrelated updates have made the router(s) even worse. In fact, I think Netgear is imploding as we speak.
“Way to go Disney! I have disabled automatic updates because the last update from Netgear slowed my router down so much. I had to downgrade to a much older version that did not include the armour guard application to get my full isp speed back. I am afraid that this new patch will come with the same application that I had to get rid of that slowed down my router. Maybe it is time for a new wifi 6 router from a different company.”
“the same issue with the 6400v2 downgraded the firmware which helped get more speed but ultimately bought a new router the Rax50 to keep up with the speeds much happier now.”
Source: PCMag comments / Netgear forum
I do however have a solution to my issue; I bought a non-Netgear branded router. Are you looking for a router with stability, performance and industry standard updates that don't break the the product altogether? Look no further.
- Enjoy ultrafast speeds up to the advertised data transfer and WiFi speed rates
- Guaranteed DNS functionality
- Don't include blueprints by Microsoft listing amateur router exploits
Buy anything but Netgear today. Special thanks to olympos1625 for logging in the forum every day and ignoring everyone while having the time to respond to new threads. I hope everyone else gets a working router sometime soon because this is verging on class action territory when the product isn't end of life. Oh, how the mighty fall.
So after a cooling off period, I decided to plug it back in and give it another whirl: I make no guarantees, but flashing the latest firmware 1.0.1.76 using this open source utility (https://github.com/jclehner/nmrpflash) which utilises a NetGear protocol (NMRP) intrinsically built into the router seems to have addressed the issue. TFTP didn't even function for those wondering. Now that I no longer need it, I'll be selling it anyway.
We already forwarded your details to our Level 2 department.
That's patent bull. I received an email as to when that ticket was opened, and it happened to be inbetween me sharting on you and you finally being bothered to reply. Where does the 'already' part come into it?
Your routers suck. This is the last time I'll be posting here. Feel free to lock this thread! I'll take a ban too.
I can confirm that the latest version (1.0.1.76). as installed using the built-in updater, does not seem to have this bug. But yeah, netgear has really gone to crap.
Finally, NETGEAR released the fix. I have been using the beta since mid sept. For my model R8300 Ver 1.0.2.156 released 11/05/2021.
