NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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, ...
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.)
You'll need to downgrade back to what was working for you.
jtdarlington wrote:
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.)
So my choices are a working DNS but massive security flaws, or increased security but DNS doesn't work?
Is Netgear working on a solution?! Has anybody heard? I'm very dismayed that such a blatant and pervasive problem has gone unaddressed for many weeks.
