NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DNS_PROBE_FINISHED_NXDOMAIN Error
My router DNS is configured to Get Automatically from ISP. From past few weeks i get DNS_PROBE_FINISHED_NXDOMAIN while trying to browse new pages for first attempt , if i reload the page it opens. I...
If you want to put a bandaid on the problem, in Windows, click on the little wifi icon at bottom right, select Network & Internet settings, click on the adapter you are using (likely Wi-Fi), click on change adapter options, right click on Wi-Fi adapter and choose properties, double click Internet Protocol Version 4, change DNS to use the following DNS server and enter 1.1.1.1 and 1.0.0.1. This will fix the issue until NG releases an update. To reverse this change do the same, but select Obtain DNS server address automatically.
*Rolling back firmware is a security risk so please don't advise that and mark the thread solved. That is not an acceptable solution! This is not solved until NetGear releases a firmware upgraded that addresses the issue!
Retired_Member wrote:
Netgear do you plan to issue an update with the fix in the next few weeks? If not I am done and will cancel my subscription and buy another brand. Please advise.....
I don't know what "subscription" you have, but when it comes to mending broken firmware, this doesn't run on any fixed timetable. It is also a drawn out process that goes through various stages. (As you have found, this doesn't always work as effectively as it should.) So, don't hold your breath for "the next few weeks".
In the meantime, your best strategy is probably to revert to earlier firmware and wait for the update.
You have not told us what firmware you have on your router. I assume that you have done the obvious thing and checked the support pages for the R8000P to see if there is anything new there:
Nighthawk X6S R8000P | AC4000 Tri Band WiFi Router | NETGEAR Support
including the recent "hotfix":
R8000P Firmware Version 1.4.1.82 - Hot Fix | Answer | NETGEAR Support
The support page is also the place to find older versions.
DNS is core part of what a router does. If this is 'a drawn out process that goes through various stages' how could a bug as basic as this get out to customers. And why is it still not fixed? I spend a few days tracking this issue down, and the last thing I would have assumed is that DNS on my router is borken.
There other long posts about DNS being broken. I believe NG is aware and has been made aware of the problems users are seen. You'll need to contact NG support and let them know what your experiencing. Otherwise, users have found that downgrading FW resolves the DNS issue until NG can get this fix fulling on newer FW.
Good Luck.
404pagenotfound wrote:
DNS is core part of what a router does. If this is 'a drawn out process that goes through various stages' how could a bug as basic as this get out to customers. And why is it still not fixed? I spend a few days tracking this issue down, and the last thing I would have assumed is that DNS on my router is borken.
Netgear release a firmware that stops their "router from routing" b:smileyfrustrated:, and customer are suppose to be ok with that? Its time to look for a replacement router which will not a Netgear brand.
Also I have just confirmed that QOS is running on the router as well even though I have it disabled in the UI.
If you want to put a bandaid on the problem, in Windows, click on the little wifi icon at bottom right, select Network & Internet settings, click on the adapter you are using (likely Wi-Fi), click on change adapter options, right click on Wi-Fi adapter and choose properties, double click Internet Protocol Version 4, change DNS to use the following DNS server and enter 1.1.1.1 and 1.0.0.1. This will fix the issue until NG releases an update. To reverse this change do the same, but select Obtain DNS server address automatically.
*Rolling back firmware is a security risk so please don't advise that and mark the thread solved. That is not an acceptable solution! This is not solved until NetGear releases a firmware upgraded that addresses the issue!
