NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Soldermonkey
Oct 24, 2021Aspirant
R8000P - DNS issues after firmware update
For some unknown reason, the automatic firmware update did not work on my R8000P router, and I found that I was one version behind at 1.4.1.68. So I manually updated to 1.4.2.84. After the update, ...
FURRYe38
Apr 21, 2022Guru
Did you factory reset and setup from scratch after applying the latest v.88 FW and see if DNS issues are present with IPv6 disabled?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Been monitoring my R7960P with v.88 loaded and no DNS issues yet however it's only been 12 hours..
Ya my ISP doesn't support IPv6 either.
jtdarlington wrote:
Been running the 1.4.3.88 FW for the past several days now. While the DNS issues were lessened, they were still present, and annoying enough that I was strongly considering dropping back down again to the previous FW that I knew "worked" (1.4.1.68). That said, I saw FURRYe38's post about enabling IPv6 and, by George, that somehow worked. I'm not sure how it worked; my ISP seems hard set on sticking with IPv4, so I never bothered enabling it. But once I did, all of the random disconnects appeared to vanish. I'm curious to see if this somehow clears up a seemingly separate issue I've been having with one of my streaming services (or if it is, as I suspect, that the streaming service simply sucks).
This seems like an odd regression, to have this tied to the IPv6 toggle. The DNS service I use uses IPv4 addresses, so I don't see why this would make a difference. The most notable and obvious instances of DNS issues I encountered dealt with either (a) large services like Google or Facebook that have many servers and likely load-balance their domains across multiple IPs, or (b) CNAMEs that "redirect" from one domain to another. In the latter example, I have CNAMEs for a few of my domains that forward to Google services; these were often some of the main "victims" of the DNS issue and required several attempts to get the domain to resolve.
Raptorialand
Jun 07, 2022Aspirant
Can confirm setting ipv6 to automatic fixes the issue for me...
After weeks of constantly fiddeling arround with my pihole, windows software/firewall and stuff...
I thought it was a user error....
Also my alexas multiroom does not bugging out after 20 minutes now.
Everything seems to work now. Pihole works and no more reloading webpages... since 1 hour it seems to work.
After weeks of constantly fiddeling arround with my pihole, windows software/firewall and stuff...
I thought it was a user error....
Also my alexas multiroom does not bugging out after 20 minutes now.
Everything seems to work now. Pihole works and no more reloading webpages... since 1 hour it seems to work.
- FURRYe38Jun 07, 2022Guru
Glad you got it working. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router
Enjoy. 📡
Raptorialand wrote:
Can confirm setting ipv6 to automatic fixes the issue for me...
After weeks of constantly fiddeling arround with my pihole, windows software/firewall and stuff...
I thought it was a user error....
Also my alexas multiroom does not bugging out after 20 minutes now.
Everything seems to work now. Pihole works and no more reloading webpages... since 1 hour it seems to work.- kerrylandJun 07, 2022GuideWould it be too much for NG to produce real release notes that say what has been fixed in a given patch, rather than forcing users to guess?