DNS>PROBE_FINISHED_NXDOMAIN error since latest update

Yes! if you have same SSID and password it should work without issue.

firmware version.  

UPDATE: It worked fine for the usual 10minutes and then back to the NXDOMAIN error, both on Chrome and Edge. 

I was thinking this might happen. 

do you still have the newer FW?

---

robjak wrote:

Check your sons settings on his laptop.   Most likely his adpater is set to not use the router for DNS.  (set manaully)  

 

if a windows laptop  run   ipconfig /all     scroll to find Wireless LAN adapter Wi-Fi     look for DNS      What is the ip(s)?   compare to the desktop.  

 

Mine would show as 192.168.0.1 (router) 

 

---

That's pretty technical for me!!! And he's not wanting me to interrupt his game right now. :-)

But I found something very interesting and I'm not sure if I can adequately explain it. 

I clicked on the Internet Access icon in the tray. It had been saying "network 2" for as long as I can remember. Just for the heck of it, I turned on wifi and clicked on the router SSID and connected to the router.  I tested all the webpages that have been giving me issues and they all came up without a hitch. I then turned off wifi and it said I was connected to ethernet, but now the Internet Access doesn't say "network 2" anymore, it is the SSID name for the router.  And everything is working just fine.  UPDATE: It worked fine for the usual 10minutes and then back to the NXDOMAIN error, both on Chrome and Edge. 

Check your sons settings on his laptop.   Most likely his adapter is set to not use the router for DNS.  (set manaully)  

if a windows laptop  run   ipconfig /all     scroll to find Wireless LAN adapter Wi-Fi     look for DNS      What is the ip(s)?   compare to the desktop.  

Mine would show as 192.168.0.1 (router) .  My issues are on wi-fi.  I have not checked if my ethernet devices are affected. 

SUNDAY UPDATE:

Just going to throw this out there. 

Our son came to visit and brought his laptop and connected to the wi-fi.  He is not getting any error messages and webpages are loading without issue. 

The desktop, which is ethernetted to the router, is still getting error messages randomly, but then immediately goes on to the webpage. Except for a random one here and there that I have to hit reload. 

Could this have anything to do with being wired into the router instead of using the wifi?

---

mab305 wrote:

NETGEAR:    This really is beyond disappointing.  I purchased a new router and the issue is resolved.  Please fix your firmware!  The hours spent on this and the disruption is not acceptable.

 

---

I'm guessing that it's not widespread....or people just don't update their firmware. They don't have to do anything unless enough people complain. 

---

robjak wrote:

I saved the  TP-Link  Archer AX6000 to my amazon wish list 2 weeks ago.  Just in case.    

---

I went with the TP-Link Archer AX50.  We're not gamers and don't have a ton of devices. But my Netgear is 5 years old (R6400) so I'm certain I will notice a difference.

NETGEAR:    This really is beyond disappointing.  I purchased a new router and the issue is resolved.  Please fix your firmware!  The hours spent on this and the disruption is not acceptable.

I saved the  TP-Link  Archer AX6000 to my amazon wish list 2 weeks ago.  Just in case.    

quote from user dvinell    

https://community.netgear.com/t5/Nighthawk-WiFi-Routers/7-29-21-Firmware-update-1-0-4-74/m-p/2125785

I ran a Wireshark Trace, and what I saw was a DNS request to 192.168.1.1 (the router) followed by a DNS response from the router: "Refused".

"10515 2021-08-18 17:21:47.901153 192.168.1.12 192.168.1.1 DNS 75 Standard query 0xf3db A www.topgear.com"

10516 2021-08-18 17:21:47.901535 192.168.1.1 192.168.1.12 DNS 75 Standard query response 0xf3db Refused A www.topgear.com"

It then repeats the DNS request, gets a positive response, and it works.

Winancy

Sorry again.  I was hoping for more from "level 2 support".  I would have lost it.  

There is another post for the same issues  where someone saw the packet  where 192.168.0.1 (router) had actually rejected the DNS request. This is where the problem is  and where NETGEAR needs to look.  Not on in cache or firewall.  

THIS IS NOT A FIREWALL ISSUE NETGEAR PEOPLE.  THIS IS NOT AN ISP ISSUE. 

SATURDAY UPDATE:

Got a callback from the Netgear Tech Support person

She didn't remember what we did yesterday, so when she gave me suggestions, I had to tell her we did that already.

Then, she told me that firewalls cause this problem and wanted me to turn off the firewall and virus protection on my computer. I refused. I told her that it's been working just fine since I got the computer, I keep it updated and I'm not going to turn it off just to see if it makes everything better. I then told her that I'm at the point where I'm going to see how it goes for awhile, maybe there will be another firmware update addressing this, and then if it's not resolved I'm buying a new router. Didn't tell her that it most likely will not be a Netgear router!

She said she could elevate this problem, but she'd have to get some settings and take some screen shots before she could do that. I was reluctant, but eventually said ok. 

Then, she had me go to chrome://net-internals/#dns and clear host cache. The only thing this did was to change the error from the nxdomain one to a err_name_not_resolved.  She then told me that this indicates the it's not the router, but the internet service provider unable to identify the address of a webpage. I reminded her that we changed DNS to Google yesterday and she gave me some convoluted explaination that it was still a problem with Spectrum. 

Then she said she'll touch base with me again and see how things are going. No timeframe. And she didn't elevate the problem to a higher tier. 

Pretty fed up at this point. 

Winancy

Sorry that you did not get any real support.   I would have told them to get fk as soon as they wanted me to install the stupid app.

Did they not think we have not tried everything they presented? 

Winancy:  Wow.  I feel your pain.  This router has been an excellent experience and I've never had issues with it.  In fact I would have recommended it and Netgear, but this update has made our network so unstable.  We get issues during monetary transactions and it impacts work from home.  I'm afraid I'm not able to wait and will need to purchase a new router.  Unless Netgear fixes this in the next day or so, I will be purchasing a different brand and advising others to do the same.  I don't want to that, but at some point I have no choice.

Hope tomorrow is better for you.  Please keep us posted!  Thank you again!

With everything I've tried, it appears to fix the issue....for about 10 minutes. And then it's back again. And it fluctuates during the day as well. Will be horrible for awhile, I'll come back a couple hours later and it's not bad at all, an hour later, I have to hit reload 5 times to get a webpage to come up. 

I just hope I get someone I can understand for support. I have some hearing loss which makes it even worse to understand accents not familiar to me.

Thank you for your update!  I noticed the firmware notification is gone too AND when I manually did a firmware update check it came back with no new firmware update is available.

I downgraded again.  Now two versions back to  v1.0.1.70_1.0.44.  I think I'm still experiencing the issue, but it doesn't seem to be as bad.  That said, it's only been a few minutes so it may be wishful thinking.

Would appreciate it if you update on on your call - good luck!

Netgear.....Please help us!!!!!!

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset
Restart the computer

I just did this and it didn't correct the problem.

Interesting observation though....there is no longer a notice that there is a new firmware update. 

And when I logged into my router, there was a saved password, which was a bit disconcerting. 

My appointment with Netgear is coming up shortly.

Thank you all for your suggestions and sharing of information!  I did downgrade to v1.0.1.72_1.0.45.  I also ran through the dns flush in the order suggested.  Unfortionately, that did not resolve the issue.

Netgear....HELP!