NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
msinex
Jul 27, 2020Apprentice
Intermittent DNS Errors and WiFi Issues
I have had the Orbi AX6000 for a few months now. While there are many things I love about it (great wifi coverage, great speed, looks nice, software, ease of setup, etc.), there are two very frustra...
msinex
Mar 14, 2021Apprentice
Original poster here, it's good to see that I'm not the only one still dealing with this problem. Seems like frustrations are high, which is completely understandable. It makes more sense to focus them on Netgear instead of other user posters, though. Focus it on the company that decided to bring out a product with buggy software and then support it with ridiculously limited technical support unless you decide to pony up even more money.
As an update to my situation, I was able to fix the majority of the wifi droppout issues I was having by shifting around the satellites a bit. I originally had them set up well within the suggested ranges and even tried both wired and wireless backhaul, but finally spread them out enough to where it worked.
I'm still getting DNS issues across those devices that I can't hardcode in a different DNS. It even caused a significant certificate issue with my work laptop and I had to work with my IT department to get a workaround. I can track the issues using a DAKboard I have running on a raspberry pi that displays our family calendar. It basically just refresshes a website through the day, and it will run into a DNS issue and not refresh until I reboot the system (I haven't been able to quite figure out how to hardcode the a different DNS server here). The odd thing here is that the issue will go away for about a week everytime I reboot my router. I won't get any errors for a week, then it will start it with an error and become pretty constant after that until I reboot again. There has to be some sort of building error or memory leak issue.
Also, in regards to the theory that this only happens with certain modem/ISP setups, I can tell you from my experience that wasn't the case. I had the same issue with my original spectrum cable service that came through a router in gateway mode as I am having today with my metronet fiber service going through a pure modem.
houcatdad
Mar 14, 2021Star
I've got the same issue with the RBK752 (RBR750 / RBS750).
The weird thing my system does is that it will attempt to resolve DNS and come up with an error (Chrome browser), but immediately refresh itself and connect.
No matter what site I go to the initial connection is a DNS_PROBE_FINISHED_NX_DOMAIN
It's frustrating AF... coverage is good, speeds are good.
Just that initial hit to ANY internet page has a DNS error with an immediate refresh and resolution.
Cable provider - spectrum
Orbi is running wireless and wired connections, dhcp. DNS are using OpenDNS servers... not google or spectrum.
PC I'm on now getting the error, Win10, latest release/patched
- msinexMar 15, 2021Apprentice
I had that same exact issue with my main desktop computer, and I manually entered in the google DNS servers on that computer instead of letting the router assign it and it solved the issue. It's just an issue for the rest of my devices now where I can't do that (or haven't figured out how to) where I'm still getting the issues.
- houcatdadMar 15, 2021Star
Yeah I figured that would resolve it... I just haven't done it b/c I wanted to try other solutions.... or wait for a fix.
It's not horribly affecting things, it's just an annoyance. I don't even have to manually refresh... it does it on it's own.
It's annoying though
- rr20552Mar 15, 2021ApprenticeBelow is Netgear’s response to my post on Facebook. 🤬
Hello Richard Baxter,
Three service plans are available when you enable Circle Smart Parental Controls on your Orbi WiFi System, one is free.
If you have issues with your Orbi system, we would love to help you.
Regards,
Patrycja
Netgear Team
- tak1313Mar 16, 2021Luminary
houcatdad wrote:I've got the same issue with the RBK752 (RBR750 / RBS750).
The weird thing my system does is that it will attempt to resolve DNS and come up with an error (Chrome browser), but immediately refresh itself and connect.
No matter what site I go to the initial connection is a DNS_PROBE_FINISHED_NX_DOMAIN
By chance, do you use Google Chrome as your browser when you get this error? If so, have you tried flushing the DNS cache for the browser? I'm just asking because it's a common problem with Chrome.
- FURRYe38Mar 16, 2021Guru - Experienced User
Anyone try using a different browser to see if the problem follows there as well?
I use Opera GX.
tak1313 wrote:
houcatdad wrote:I've got the same issue with the RBK752 (RBR750 / RBS750).
The weird thing my system does is that it will attempt to resolve DNS and come up with an error (Chrome browser), but immediately refresh itself and connect.
No matter what site I go to the initial connection is a DNS_PROBE_FINISHED_NX_DOMAIN
By chance, do you use Google Chrome as your browser when you get this error? If so, have you tried flushing the DNS cache for the browser? I'm just asking because it's a common problem with Chrome.
- energieMar 16, 2021LuminaryIt is not a problem with the browser. The browser is showing that there is a problem with the DNS server / firmware of Netgear.
Chrome browser at least makes a second attempt when a DNS error occurs. Firefox for example doesn't. So that leaves users manually refreshing the webpage.
Netgear should fix the DNS server/proxy with the firmware.- tak1313Mar 16, 2021Luminary
energie wrote:
It is not a problem with the browser. The browser is showing that there is a problem with the DNS server / firmware of Netgear.
Chrome browser at least makes a second attempt when a DNS error occurs. Firefox for example doesn't. So that leaves users manually refreshing the webpage.
Netgear should fix the DNS server/proxy with the firmware.But have you tried flushing Chrome's dns cache?
https://geeksadvice.com/how-to-fix-dns_probe_finished_nxdomain-error/
- houcatdadMar 16, 2021Star
yes, this was on Chrome, but in troubleshooting I tried Edge, IE, and Firefox... and got the same experience.