NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Winancy
Aug 03, 2021Apprentice
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 webpages. Sometimes, after 2 seconds, the webpage will load, but sometimes I have to hit the reload button repeatedly, and sometimes nothing works. It's inconsistent. I also have two apps, weather and radar, that sometimes load and sometimes don't.
I have:
Reset/flushed DNS
Reset Winsock
Turned off the computer
Rebooted the modem
Rebooted the router
Restarted the computer
Still getting the error. Is it possible to update again, maybe something didn't go right the first time? Is it possible to use a prior firmware version that did work? Any other suggestions?
169 Replies
Replies have been turned off for this discussion
- GamefanInitiate
I'm getting the same thing as you since the update. I'm about to buy another brand and throw this router down my apartments garbage shute. This error is fustrating.
- WinancyApprenticeI guess I'm glad I'm not the only one, but it doesn't fix the problem! It's a pain having to smash the reload button to get a webpage to load. And then half the time, the pictures don't load. I can't log in to some of my sites. I'm trying to do everything on my phone, but I notice some glitches there too.
- drdeathdlgAspirant
This is happening across various models I have a R8000 at home and R6700v3 at work. I have had to reinstall previous versions of firmware to get this to stop from happening on both.
- robjakLuminary
Finally, NETGEAR released the fix. I have been using the beta since mid sept. For my model R8300 Ver 1.0.2.156 released 11/05/2021.
For all those waiting, look for new FW to fix the DNS issues.
> [...] Is it possible to use a prior firmware version that did work?
> [...]Visit http://netgear.com/support , put in your model number, and look
for Downloads. (For older versions, under Firmware and Software
Downloads, look for "View Previous Versions".) Find the kit(s).
Download the kit(s) you want. Read the "Release Notes" file for
instructions. (In the User Manual, look for "firmware", and,
especially, for a topic like "Manually Upload Firmware to the Router".)
When that fails because of a deficient User Manual, try:- WinancyApprentice
antinode Thannk you so much for putting me in the right direction. I downloaded and installed the previous version 1.0.45. At frist, I was getting the same errors, then realized, I probably have to restart the computer. After I did that, everything is working just fine....so far. Fingers crossed! Now, I just wait for the next firmware update and hope it will behave.
- WinancyApprentice
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.
Thank you for the info about getting previous versions. The link was there, I just never saw it :< until I read your message and explicitly did a FIND on the page. Thank you. I'm going to try, systematically the previous versions to find out which one works.
- mkxTutor
Don't waste your time on that version.
I too am experiencing this issue since upgrading firmware. Has Netgear acknowledged the issue and/or a plan to remediate?
- landousInitiate
I have an R6400v2 and have been seeing the same problem after the latest firmware update. The latest firmware update available is 1.0.4.118. I first tried to go back to a recent build from September 2020, v1.0.4.102, but was still seeing the DNS errors on several of my devices.
I then went back to the latest build for the previous major version, v1.0.3.66, which is from 2019. I did the change yesterday and everything seems to be working ok so far.
Netgear support: please check if the dnsmasq version was changed after the latest builds, my guess is that there's a bug/memory leak/service crashing problem.
- Retired_Member
Replying here that I am still seeing this issue and a FW rollback did not help. Almost time to replace my hardware.
Glad a new non-Netgear router restored normal service for you. I too purchased a new router which resolved the issue for me too.
- robjakLuminary
Winancy
It is good that you got your net fixed. Too bad that Netgear could not help you. They will lose alot of customers. I will never buy another Netgear product.
- WinancyApprentice"as you can seehere lots of complains from that time."
Good job on spamming. What does this URL have to do with this issue?
https://removalsoldham.co.uk/man-and-van-services-oldham/
gaver376 wrote:I am also facing this NXDOMAIN error issue from the last updates also it was not performing as well with the second last updates as you can seehere lots of complains from that time.
- BuffoTutor
Just downgraded my R6700v3 from FW 1.04.118_10_0.90 to previous FW 1.0.4.106_10.0.80. So far all my DNS issues have disappeared!! I tried numerous "fixes" before downgradeing FW. Netgear needs to fix this problem.
- JonnieChimpoAspirant
Same issue as everyone else with V1.0.1.74_1.0.48. I haven't downgraded my firmware yet but probably will soon since it seems that Netgear has not acknowledged the problem and it seems like their support staff is going to go in circles reading their scripts on how to disable firewalls and blaming the ISP. Has anyone successfully and painfully gotten Netgear to escalate this issue?
- BuffoTutor
I just called them about this issue and pleaded our case to the tech. I told him to scan the forums and READ about all the same problems being fixed by downgrading FW. I spent 20 minutes dancing around the finger pointing. I hope he got the message.
- WinancyApprenticeNetgear mentioned escalating but never did.
Don't bother rolling back to an earlier firmware version. It doesn't help. The DNS is broken.
I decided I no longer wanted to screw around and bought a new TP-Link router. While the DNS issue is gone, it doesn't seem as fast as the Netgear.- robjakLuminary
Rolling back firmware does work for most people but not all. It does work for me.
I finally came back from vacation and recieved an email from netgear about them calling me. I told them that if they are going to call me to step me through reinstallation then i dont want what they are selling. They stated that i would get a call from their engineers and we set up a time for thurday night.
I put the crap FW back on the system and verified the DNS issues were still there. Then I captured numerous DNS request refusals from the router using a packet sniffer. I then waited for 3 hours and the call never came.
NETGEAR SUCKS. I WILL NEVER BUY ANOTHER NETGEAR PRODUCT AGAIN.
I then switched back to older FW and the DNS issues disappeared.
- Supertek2k16Initiate
Netgear has made me go out and purchase another brand after this last, failed, useless firmware update on my R6400V2 wi-fi router. It's not even listed on their drop down choice to talk about it. Buh bye Netgear. You suck, Bigly. Firmware upgrade 1.0.4.118 is a disaster. What a mess. Not buying anything Netgear from now on.
- WinancyApprentice
Supertek2k16 wrote:Netgear has made me go out and purchase another brand after this last, failed, useless firmware update on my R6400V2 wi-fi router.
What did you buy? I made the mistake of buying a TP-Link AX3000 and after one month, the WAN port on the router failed. My modem showed internet working, but the light that shows data transferring was out. After plugging the modem directly into the computer, the internet worked fine. When I went into the TP Link dashboard it said there was no WAN connection, when in fact, there was. Thank goodness I bought it on Amazon and it's still in the return window!!!
- robjakLuminary
I have been contacted to test a fix but I am a business trip and cannot download or flash the fix from engineering. So for those waiting, there may be a fix coming out shortly.