NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Apr 01, 2022Guru - Experienced User
New - R8000 Firmware Version 1.0.4.84 Released
Security Fixes: 3/30/22
Fixes security vulnerabilities. (Don't know if this resolves the DNS issues seen on v.76 version.)
For more information about security vulnerabilities, visit https://www.n...
bois-e
Apr 18, 2022Tutor
After installing and upgrading FW on my nighthawk X6, I consistently get DNS_PROBE_FINISHED_NXDOMAIN errors. I tried setting to google dns resolution (8.8.8.8 8.8.4.4), but still encountered the error.
I also tried flushing the dns cache on my client devices.
I also tried clearing cookies, browser cache in chrome.
I then went back to the get DNS from ISP.
I also tried going to the router admin and turning the ipV6 connection type from Disabled to 6to4Tunnel (which I saw in another community post worked for them)-- but did not work for me.
Any thoughts would be greatly appreciated.
FURRYe38
Apr 18, 2022Guru - Experienced User
What model router do you have? R####?
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?
Does enabling IPv6 on the router change anything?
- bois-eApr 18, 2022Tutor
Firmware Version: V1.0.4.84_10.1.84
Hardware Version: R8000
Modem: ARRIS SURFboard SB8200 DOCSIS 3.1 Gigabit Cable Modem (Purchased)
My network was working fine with a previous netgear nighthawk modem that I factory reset and gave to a friend. I was hoping this would be an upgrade. So far, it's been a bit of a pain.
I saw the DNS probe error on a device, but I rebooted it, I will continue to look for issues and report.
- FURRYe38Apr 18, 2022Guru - Experienced User
If you see this again, try enabled IPv6 on the router and see if this changes anything.
This has been a known issue on some recent versions of FW. If you see this again and IPv6 doesn't change the behavior, you can downgrade to v.62 or v.68 and will resolve this. NG is aware if the issue and is working on it.