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 issue with new firmware update
Hi all, Last week I updated to Firmware 1.2.4.84 and now almost constantly receive error message DNS_PROBE_FINISHED_NXDOMAIN - I have to reload the sites several times before they appear. Maybe the error does not appear once sites are cached? But it's hard to tell.
Have restarted modem and router three times.
Is there an easy fix for this? Should I just wait for an update on the firmware to fix the issue? If reverting is the solution, I have no idea how "revert to a previous version" of the firmware. I can download the previous version files but have no idea how to translate that into downgrading the firmware on the router.
Need help please, it's wreaking havoc on authentications and my ability to study for my finals. Thanks to all for any help.
- Thanks to all for the suggestions. Quick update — tried the DNS setting change and thought that was a fix, but then it wasn’t.
So, in conclusion, the only real solution is to downgrade your firmware and wait for the issue to be fixed.
Thanks again to all and hope this helps others with the same issue.
19 Replies
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
If you do a search in this forum for "DNS_PROBE_FINISHED_NXDOMAIN" you'll find there is a fair amount of posts regarding this.
You may need to downgrade FW back to what was working.
Some mentioned the use of IPv6 enabled on the router may help.
Has a factory reset and setup from scratch been performed since last update?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Charter Spectrum Model ET2251 -- is the problem maybe because the modem is old?
I have read through previous posts but there is no clear concise answer.
Are you suggesting a factory reset on the router? Or the modem?
Thank you for your help and quick response.
ladyspica wrote:
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Charter Spectrum Model ET2251 -- is the problem maybe because the modem is old?
No. Just checking to see if there is a router here or not. Your fine here.
I have read through previous posts but there is no clear concise answer.
Ya, mostly this is a FW issue and needs to be addressed by NG. They are aware of it. No idea when it will be fixed.
Are you suggesting a factory reset on the router? Or the modem?
Router.
Have you tried enabling IPv6 first?
Try that.If that doesn't help, then try downgrading firmware.
You simply downgrade it from the support site, extract it, and then follow the manual update process but use the older firmware you downloaded.
There's a support site with access to manuals, firmware, install guides, etc.
Go to https://www.netgear.com/support/
Type in your model number and from there it'll take you to the above.
Its a great resource to start with.Welcome to the club. It's a probblem with the latest firmware release. No fix from NG yet that I'm aware of. If you want to put a bandaid on the problem, 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 release an update. To reverse this change do the same, but select Obtain DNS server address automatically..
- Thanks to all for the suggestions. Quick update — tried the DNS setting change and thought that was a fix, but then it wasn’t.
So, in conclusion, the only real solution is to downgrade your firmware and wait for the issue to be fixed.
Thanks again to all and hope this helps others with the same issue.Manually setting DNS on your client definitely works. Here's the catch though and what may be happening to you. If you use multiple wireless SSID's, you have to make the change for each one because each SSID has its own DNS setttings. So if you connect to "yourwirelessSSID" and make the DNS change to that adapter, that fixes the issue, but then if you connect to "yourwirelessSSID-2", the problem will re-appear until you make the DNS change on that adapter too. It's a PITA, but it works once you change all your adapters to use manual DNS.
