NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DNS>PROBE_FINISHED_NXDOMAIN error since latest update
Model R6400, firmware v1.0.1.74_1.0.48, Windows 10, ethernet connection Since I updated the firmware, I have been getting DNS_PROBE_FINISHED_NXDOMAIN errors when I open up browsers and go to webpage...
Unfortunately, I spoke too soon.....
Not sure where to go from here....I downloaded and installed the previous firmware, which booted the router, then I restarted the computer, and it seemed to be ok for a few minutes and then the errors started all over again. Factory reset??? Ugh.
Using whatever the ISP provides.
I've shut down for the night, so I can't check until tomorrow.
But I did flush DNS and reset winsock again and all worked fine... For about 15 minutes, then it started all over again.
Haven't tried using a different DNS service. It should work with what I've been using for years, no?
I've shut down for the night, so I can't check until tomorrow.
But I did flush DNS and reset winsock again and all worked fine... For about 15 minutes, then it started all over again.
Haven't tried using a different DNS service. It should work with what I've been using for years, no?
- My laptop has the same problem.
My phone does not.- I own both a r6400v2 and r6700v3, both updated to the latest firmware recently. Each router is on a completely different ISP (comcast and frontier) but each router exhibited the same intermittent DNS errors 0101 = Reply code: Refused (5) . There is little pattern to what is refused and why, it seems to be random causing web pages to be blank (when css files are not resolved etc). Basically making the internet unusable.I backed both devices to previous firmware versions R6700v3-V1.0.4.106_10.0.80 and R6400v2-V1.0.4.106_10.0.80 which seems to have solved the problems. So that means unless netgear fixes these issues we hit the wall on updates.
- justanguser2 You listed the same previous update for both of your router models. Is that correct?
Unfortunately, it didn't fix my problem, although it's better. Most web pages load, though some get the error and within 2-3 seconds, will then load. Some graphic intensive websites end up looking wonky or the graphics won't load until I hit reload several times.
And as you say, it's not consistent. Everything works for a few minutes, then nothing loads, then everything loads with a delay.
Frustrating as I do some streaming broadcasts and this is making it impossible and glitchy.