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, I found that I was having DNS problems on multiple devices. These problems persisted for weeks. I tried specifying different DNS servers, away from my ISP's servers, but the situation did not improve. So, I downgraded the firmware back to 1.4.1.68, and the DNS problems went away.
quite a few people have posted issues like this across mulitple product lines. So don't feel alone. I'm sure netgear is working on it as we've seen it on multiple products.
Current setup: CM2000-> RBKE963B-> Trendnet TEG-S380-> GS716T-> pi-hole also in AP setup: RAXE500->EAX80 1.4gig download/50mbps upload from Xfinity We’re members of the public helping out on our own time.
Same here. Recently updated to V1.4.2.84_1.3.42. Ever since, I've been consistently getting failures that look like DNS failures. In web surfing, it takes multiple refreshes of the page before it actually connects, then everything is fine. This is glaringly obvious with my Google G Suite sites, which use CNAMEs and thus several DNS look-ups before you actually connect to an IP. My Thunderbird hasn't connected to GMail IMAP at all since the router update; Google tends to have lots of IPs and short DNS TTLs, so I'm guessing this is related. (Nothing has changed with my account or authentication settings to cause this to fail.)
The only addition I would make is that WiFi connected devices seem more susceptible to this than hard-wired devices. Some sites won't work at all if I'm on WiFi, but if I switch to a desktop with a physical cable to the router, the site works much more reliably. (It may still take several refreshes before I can load the site.)
Model: R8000P|Nighthawk X6S AC4000 Tri Band WiFi Router
Same here. Recently updated to V1.4.2.84_1.3.42. Ever since, I've been consistently getting failures that look like DNS failures. In web surfing, it takes multiple refreshes of the page before it actually connects, then everything is fine. This is glaringly obvious with my Google G Suite sites, which use CNAMEs and thus several DNS look-ups before you actually connect to an IP. My Thunderbird hasn't connected to GMail IMAP at all since the router update; Google tends to have lots of IPs and short DNS TTLs, so I'm guessing this is related. (Nothing has changed with my account or authentication settings to cause this to fail.)
The only addition I would make is that WiFi connected devices seem more susceptible to this than hard-wired devices. Some sites won't work at all if I'm on WiFi, but if I switch to a desktop with a physical cable to the router, the site works much more reliably. (It may still take several refreshes before I can load the site.)
My Setup | ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode | Wifi Router MK83+ (Router Mode) | and RBK853 (Router Mode) | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, MR6150, R7000, R7800, R7960P, R8000, R8500, R9000, RAXE500, RAX50, XR450, XR700, XR1000, EX7500/EX7700
I know they're aware of the issue. And I've seen beta fixes for the R6400/R6700 that a Mod sent to a few users.
So I have a feeling its in the works but they don't release any details on ETA's.
Current setup: CM2000-> RBKE963B-> Trendnet TEG-S380-> GS716T-> pi-hole also in AP setup: RAXE500->EAX80 1.4gig download/50mbps upload from Xfinity We’re members of the public helping out on our own time.
Can confirm that downgrading to V1.4.1.68_1.3.28 "fixes" the DNS issue. Fortunately, the security flaw V1.4.2.84_1.3.42 is supposed to fix requires access to the local LAN, so I guess we'll just have to live with that for now. (Of course, anyone who follows INFOSEC news knows there are ways around the "local LAN" issue. Just make sure everyone in your household/office knows to browse safely.)
@kerryland Pihole works pretty nice. I've got one but its running in a docker container on my server. Love how much it blocks.
Current setup: CM2000-> RBKE963B-> Trendnet TEG-S380-> GS716T-> pi-hole also in AP setup: RAXE500->EAX80 1.4gig download/50mbps upload from Xfinity We’re members of the public helping out on our own time.
Any luck with this, Netgear? I've had several attempts to add this comment... This is my first and will be my last Netgear device. It would appear you cannot afford to hire reasonable talent. I mean, seriously, DNS issues in a router ?! You're kidding me right? Sounds like piston misfires in an engine. Would you buy a car from that manufacturer ?
Several more months on and still no fix or new firmware update? For real? They can't even make a firmware version available that's between 1.4.2.68 and 1.4.2.84? This is not good. Is this model officially end of life and there will never be another firmware update or hotfix? Bueller?
Model: R8000P|Nighthawk X6S AC4000 Tri Band WiFi Router
What do you mean between .68 and .84? There was probably nothing made or developed for release between those versions so if there was, was not mented for public use.
For now, users should keep to v.68 or .v62 for now. Fixes and FW development doesn't happen over night.
My Setup | ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode | Wifi Router MK83+ (Router Mode) | and RBK853 (Router Mode) | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, MR6150, R7000, R7800, R7960P, R8000, R8500, R9000, RAXE500, RAX50, XR450, XR700, XR1000, EX7500/EX7700
68 came out over a year ago. 84 came out 6 months ago and the DNS issues have been getting reported since then. I don’t think 6 months = overnight or that it is unreasonable to expect at least some sort of hot fix to be made available within 6 months, especially when the issue directly impacts your ability to use the internet, which is kind of the main purpose of having a router. Having to use an insecure firmware version for 6 months as the only solution to continue to use this hardware is not a good look.
New firmware was released this past week (v88). Installed it this morning and so far so good, no DNS issues/sites not loading. Will continue to monitor throughout the weekend, but hopefully it's been addressed and we can go back to being secure and functional!
Model: R8000P|Nighthawk X6S AC4000 Tri Band WiFi Router
Sadly I have already bought a competitors product because I couldn't wait any longer. Its amazing how much relief I feel ps. This is my second attempt at this post (last time I mentioned a specific brand). I hope the moderators aren't banning statements like this.
Yes, I completely agree, I had struggled for months on DNS this issue and almost gave up on my NG.
There has to be a quicker way to engage with NG DEVELOPERS on prioritizing with getting these issues resolved. (Moderators, if you have any ideas or suggestions, that would be great!)
And a big Kudos to the expert moderators supporting this group, I appreciate all the help & solutions they offer!
Kerryland, Thank you for responding with your comments!
Summary: Several people reported DNS issued related to PROBE or non-response from websites
NG pending actions: NG engineer team is aware of the problem, they are working on it. It does take some time for development and testing. In meantime, users can try enabled IPv6 to see if this corrects the DNS problem or revert back FW to what was working.
Please be patient.
My Setup | ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode | Wifi Router MK83+ (Router Mode) | and RBK853 (Router Mode) | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, MR6150, R7000, R7800, R7960P, R8000, R8500, R9000, RAXE500, RAX50, XR450, XR700, XR1000, EX7500/EX7700
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.
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.
My Setup | ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode | Wifi Router MK83+ (Router Mode) | and RBK853 (Router Mode) | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, MR6150, R7000, R7800, R7960P, R8000, R8500, R9000, RAXE500, RAX50, XR450, XR700, XR1000, EX7500/EX7700
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.
