NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DNS Issues after firmware upgrade
I recently upgraded to the V1.42.84_1.3.42 firmware verison on my router. Since the update I am seeing random DNS timeout errors (the probe errors). In most cases, the time out is replaced within 1-2 sec by the actual request going through. I have verified that this is happening across any DNS service I specify at the router (ISP, cloudflare), and happens accross various local machines, whether on wired or wireless connection. The problem goes away if I specify dns settings on the local machine.
I used fiddler to analyze browser traffic, and can see it occurs when a DNS cache validation happens. It would appear i am first getting a DNS timeout, rapidly followed by the actual request going thorough. Interestingly, I have not seen this behavior on the sole IOS device on the network, an IPAD. Not sure if it matters, but I have armor installed.
As this behavior appears to directly correlate to the firmware update, and in searching the forums I have seen similar issues on other Netgear routers reported with the latest fireware, I am wondering a few things:
1. How many others with the 7960P routers seen this issue with the .84 firmware?
2.Is Netgear aware and working on a fix?
3. If I decide to roll back to the.68 version to fix (as several others have reported on similar model routers) what secuirty updates do I give up?
Thanks.
It's working! Odd, but after I put the Orbi in AP mode and completely disconnected from the Internet (whoops), I reset the Orbi to get back to square one and after setting it up I noticed that the Nest downstairs was connected. I went upstairs and tried to connect the other Nest and...it worked! All I did was reset the Orbi after putting it in AP mode in error.
One of my Nest's did have a message that it was last updated on January 24, so maybe that has something to do with it too.
Thanks all!
37 Replies
Replies have been turned off for this discussion
2 things you can try.
1. enable IPv6.
2. set your own dns provider for both the standard DNS entry and the IPv6 entry.
If those don't help, then I'd downgrade.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Was a factory reset and setup from scratch performed after v84 was installed?
Maybe onepiece can lend a hand?
How do you disable Armour, I see no option for that.
PS. Another friend of mine has started experiencing the dns issue aftter router upgrade. I don't beleive she has Armor installed. I could downgrade, but before I do, I want to know what secuirty fix i would be giving up.
Until then, or until they issue a fix, I am working around it by stting DNS at the individual workstation level.
What happened to Netgear QC? :(
We are having similiar issues with multiple clients. The router seems to be blocking websites on the DNS level. Not sure if the BitDefender that is installed on the routers have something to do with it, but websites like logmein, teamviewer, logmein client can't connect, godaddy, etc. And it's all on a perfectly clean OS.
It is just like this writer said, they will not connect at first, but if you keep refreshing, eventually you'll get in. All browsers working the same way. It appears that doing a flushdns or restarting the computer will allow one entry, but then all websites will start doing the same thing again. Want to blame Comcast, but no issues reported.
There is no virus protection or non default firewalls in place. Windows 11, Windows 10. Have not tried an Apple, but I'm sure the same problems would happen. Have removed the default McAfee and all Lenovo Software that came on this Yoga, currently running Win11 with all updates. Was working perfectly fine for the last three months, then since the firmware upgrade on the NETGEAR, refresh, refresh, refresh, refresh, refresh, refresh, aaaaahhhh!!!!
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?Has a factory reset and setup from scratch been performed since last FW update?
Is Armor enabled on the router?
Try a reset and setup from scratch and do not enable Armor, Access Controls or Traffic Meter.
If all else fails, revert FW back to what was working on the router.
nvizi wrote:
We are having similiar issues with multiple clients. The router seems to be blocking websites on the DNS level. Not sure if the BitDefender that is installed on the routers have something to do with it, but websites like logmein, teamviewer, logmein client can't connect, godaddy, etc. And it's all on a perfectly clean OS.
It is just like this writer said, they will not connect at first, but if you keep refreshing, eventually you'll get in. All browsers working the same way. It appears that doing a flushdns or restarting the computer will allow one entry, but then all websites will start doing the same thing again. Want to blame Comcast, but no issues reported.
There is no virus protection or non default firewalls in place. Windows 11, Windows 10. Have not tried an Apple, but I'm sure the same problems would happen. Have removed the default McAfee and all Lenovo Software that came on this Yoga, currently running Win11 with all updates. Was working perfectly fine for the last three months, then since the firmware upgrade on the NETGEAR, refresh, refresh, refresh, refresh, refresh, refresh, aaaaahhhh!!!!
I'm having the same problem. I did the whole 9 nine yards (cleared cached, changed browsers, command prompt as admin flushed DNS on all devices, moved the DNS off ISP and onto the Google one). I did not try moving to IPv6 tho.
Oddly, the only devices impacted were PC ones in my household and not Macs.
I gave up and rolled back the firmware and everything magically works again. I know I'm giving up whatever new security patch is available but I was so tired of the 2FA timing out and not allowing me to enter the codes to get access to all my work.
I was un-willing to give up the secuirty update, so I just configured the DNS settings on the invidual (windows-based, Apple IOS still seem to work fine) workstations. I like cloud flare for this. This seems to work just fine.
Have you tried this approach to be able to keep the new update?
I have the same problem after upgrading the firmware. Setting the DNS at the windows level fixed the issue.
Thanks for the recommendation. Like someone asked what happened to NETGEAR QC? I will think twice next time when I have to upgrade my router. Few times my router reset it self loosing all the configuration. Later i found out that it was due to auto firmware upgrade was on. So I disabled to avoid any issues in future.
I have my router config backed up before the firmware upgrade. If i have to hard reset the router, can I restore these configurations?
It is absolutely disgusting that netgear is looking the other way on this issue. The problem began with its latest firmware updates and previously there were no issues. NETGEAR knows this issue and is refusing to do something about it. This will be the last NETGEAR product i ever by. Simply because they don't rectify an issue that they caused. Literally happening to almost every router. And the only response from NETGEAR is to downgrade the firmware (to basically an unsecure version considering it was a security patch they were fixing which led me to upgrade).
Shame on NETGEAR for not fixing this.
This is my 3rd Netgear router. For me DNS is not an option. I may have to look for alternative. Definitely not getting Netgerar anymore.
Downgrading to a vulnerable firmware is not a solution.
Firmware V1.4.2.84_1.3.42 has buggy DNS and no amount of toggling, resetting and tweaking will fix it.
Netgear needs to properly support their product and provide a firmware that doesn't break everyone's DNS.This solved it for me, hope it helps:
1. Log in to your router
2. Change DNS servers from auto to servers like cloudflare 1.1.1.1. & 1.0.0.1. or others (there are many options, just do a quick Google search).
3. Save settings. I also updated each of my devices to use these servers, but it was already working properly after step 2.
- I’ve tried every suggestion in these forms, including setting Cloudflare and Google DNS server IP’s. Nothing worked DNS resolution continually broken. Fix for me was to return the router to Costco and get a different brand. Best of luck to all of you
Have been having the same issues with a Nighthawk R7960P after updating to V1.4.2.84_1.3.42 I am rolling back to V1.4.1.68_1.3.28 available from the Netgear service site. It was so bad that I could not complete my work from home without isssuing an ipconfig/flushdns every 10 minutes. If a let a screen sit, I would get a DNS resolve error when I went back into it. I sure hope Netgear gets a new version of the firmware rolled out soon. I don't like to avoid running outdated firmware on my routers.
Totally apreciate your frustration. As I also was unwilling to give up the security update, I sucessfully used the work around to set the DNS at the client machines instead. A pain, but it works well.
An interesting side note, my Android Phone uses the DNS of the router, and it works fine. It is just the Windows and iPads with an issue.
I am having the same issues with V1.0.2.158. If I connect directly to my modem it's fine, but R8500 it doesn't work. Retrying tends to work but after a few retries.
Setting the DNS to googles or even the DNS from my provider on my individual devices resolves the issues or seems better.
It seems like this issue has impacted a number of router models. Fortunately the solution of resolving DNS at the device level seems to be viable for at least the vast majority. The fact it has remained unresolved and appears to impact a number of different models suggests the problem may be complex, and the solution complicated.
I know some have understandably given up. To be frank, I have researched other routers, and most seem to have their own issues. To date, I have not found another I feel comfortable switching to.
I have tried many routers over the years, and had the best luck to date with the Netgear models.
Given the workaround, I am going to hang in there and hope a new firmware that resolves this will be released soon.
Fingers crossed 😐
Yes, I had similar DNS problems, struggling for months.
My solve/resolve tied back into ENABLING IPv6 under the advance settings. See my thread below
With latest version of the firmware V1.4.3.88_1.3.50 and factory reset.
Hope this helps you!
Initial results after enabling IPV6 are positive although very limited testing so far. I was able to open a site that wouldn't even open before. Only Windows 10 showing DNS issues. iPad and Android phone seem to work OK. V1.4.3.88_1.3.50
