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...
If I enable IPV6, what option should I be using?
Auto Detect?
6 to 4 tunnel or?
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?
You can try. Would be best if you reset and setup from scratch first and check for DNS issues. Then try loading your saved config files if the problem appears. Problem may continue and you may need to revert FW.
- Yep, I did the same. I have been configuring all clients with issues at the computer level to Google DNS instead of automatic. That seems to fix the problem. Should not have to do this.
