NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Getting DNS_PROBE_POSSIBLE error on R8000
In about the last month and a half, I have started noticing two things: * pings spike every 5 minutes, from about 8-9ms, to over 1000ms, for 5-10 seconds (this messes up Remote Desktop) * DNS_PR...
Finally a new R8000 firmware available.
https://kb.netgear.com/000064738/R8000-Firmware-Version-1-0-4-84
Anyone tried yet?
Ok i tested. DNS problem still there with this latest firmware. Hopeless...
I don't get things like this. Maybe they don't want to maintain it because they think people will give up and buy a newer router FROM THEM? I think more likely people will move on to another brand. And you know they CAN fix it, since previous versions of the firmware didn't have the problem.
Very odd to me. Its great hardware--FreshTomato firmware proves that. Why have crap firmware, not fix it, and tarnish your reputation? Strange.
Did you factory reset and setup from scratch after the new FW was loaded?
vinada wrote:
Ok i tested. DNS problem still there with this latest firmware. Hopeless...
Netgear Engineering was able to fix the DNS issue in Sept 2021. They just have not released it yet.
The DNS problem was reported by multiple people across multiple models of Netgear routers nearly a year ago. Netgear knew about the problem and yet consistently release firmware versions which did not fix the problem.
Netgear has demonstrated a real contempt for its customers. My advice to all Netgear customers is they should consider carefully do you want to stick with an organisation which doesn't care about its products and customers. For me, I have already given up and moved on from Netgear. Caveat Emptor !
I always do, as I, too, like to: 1. reduce chance of easily solvable issues (due to engineers not correctly migrating old settings - or "future" (possibly unknown) settings, in the case of downgrading firmware). 2. log how the default settings change, since my baseline for future configs is based on default + my very own (few) changes (rather than log endless default settings - makes pinpoining "new" issues much easier too - as they're likely due to one of those few changes I've made). Latest firmware is still broken...
FURRYe38 wrote:
Did you factory reset and setup from scratch after the new FW was loaded?
vinada wrote:Ok i tested. DNS problem still there with this latest firmware. Hopeless...
Ok thanks for letting us know.
Go back to v.62 or v.68 as I believe these two version don't experience these issues with DNS.
Fatman305 wrote:
I always do, as I, too, like to: 1. reduce chance of easily solvable issues (due to engineers not correctly migrating old settings - or "future" (possibly unknown) settings, in the case of downgrading firmware). 2. log how the default settings change, since my baseline for future configs is based on default + my very own (few) changes (rather than log endless default settings - makes pinpoining "new" issues much easier too - as they're likely due to one of those few changes I've made). Latest firmware is still broken...
