NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
7/29/21 - Firmware update 1.0.4.74
Anyone having issues with this firmware update version 1.0.4.74? Ever since I updated my router's firmware to this version my browser(mozilla firefox) has been having issues connecting to webpages. To be exact I kept getting "We're having trouble finding that site" connection issues on Mozilla Firefox. I had to hit refresh two to three times just to get the webpage I wanted to open to load correctly.
So this morning I downgraded my firmware version from 1.0.4.74 back to 1.0.4.68 to see if this issue would persist on mozilla firefox and it has not since downgrading.
Recommended build to use currently is v.62:
https://www.netgear.com/support/product/r8000.aspx#Firmware%20Version%201.0.4.62
50 Replies
Did you try a factory reset prior to the downgrade?
Anytime there's issues after a firmware change, thats the first step I recommend.
I did try a factory reset with my router before downgrading the firmware along with rebooting my router multiple times and rebooting my devices to see if that would fix this issue with Mozilla Firefox. Unfornatelety none of those troubleshooting steps worked. This is clearly an issue with this new firmware as I have run into absolutely no issues with mozilla firefox since downgrading my firmware.
was the issue only on Firefox?
Or did other browsers have the issue as well.
The issue is that there is no way to get support for routers that are past their complimentry support period (90 days i think). There is no email or phone support). Kind of depressing. I have been contacted via another post for "actual Level 2 NETGEAR support" but i am now on a 12 day vacation so i am not sure if anything will happen fast. Others may also have contacted the moderator.
That post is here: https://community.netgear.com/t5/Nighthawk-WiFi-Routers/DNS-gt-PROBE-FINISHED-NXDOMAIN-error-since-latest-update/td-p/2123701/page/2
There is reply from a moderator. You all should follow the direction from that reply.
I do believe that NETGEAR does know about an issue and may be working on it. More people need to let them know. The problem is it seems this community forum may be the only way let them know.
***NETGEAR broke their DNS in the latest FW release for many routers. Manually setting DNS on clients is not a fix. Rolling back FW to a security flawed version is also not a fix. Demand that they fix it.
Hi,
I've just been through this myself.
On MS Edge it shows as "Hmm ... can't reach this page", a pause, and then it works.
I tried configuring Google DNS Servers in the DNS settings in the router ... same result.
I ran a Wireshark Trace, and what I saw was a DNS request to 192.168.1.1 (the router) followed by a DNS response from the router: "Refused".
"10515 2021-08-18 17:21:47.901153 192.168.1.12 192.168.1.1 DNS 75 Standard query 0xf3db A www.topgear.com"
10516 2021-08-18 17:21:47.901535 192.168.1.1 192.168.1.12 DNS 75 Standard query response 0xf3db Refused A www.topgear.com"
It then repeats the DNS request, gets a positive response, and it works.
Confguring Google DNS directly on my PC solves the problem, but I have 16 devices on this network!
I will probably have to back out to an earlier firmware version.
Regards,
DaveV.
Same problem here with the latest firmware 1.0.4.74 DNS fails to resolve when browsing. Fix your garbage update Netgear!
- I have been dealing with this same issue for several weeks now. Factory reset, reverting to the previous firmware, and all the other flushing and renewing hasn't corrected the problem. I've been contacted by Netgear support and worked with them twice. Changing to Google DNS, clearing caches, factory reset, and a whole bunch of other things read off the script. When she suggested that I turn off my firewall and anti-virus and I refused, she said to call my ISP because that's probably what the problem is.
.
I ordered a new router. Not Netgear. It arrives tomorrow. I hope it solves the problem.
If you didn't face any issues you're in the minority.
Has anyone tried the new 1.0.4.76 fimare update? Does it fix this issue?
- I asked the same question earlier in this thread but nobody responded so I guess no Netgear does not support us even though they created the issue. Very sad, I used to think Netgear was a great company until this incident.
Same issue still in March 2022.
