NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
What Firmware version is currently loaded?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet or more is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
https://kb.netgear.com/31029/Where-should-I-place-my-Orbi-satellite
Any Wifi Neighbors near by? If so, how many?
Would be related to a different issue with wifi dropouts.
Tobamory wrote:
I have 2 net connections at home one is Virgin Media UK with the new HUB 4 in modem only mode, the second I tried was a BT Adsl and Sam again
I know you all talk about DNS but am I right in thinking the WiFi dropouts are related or is yet another issue ? Anybody know
I’ve missed the Amazon return also so I’ll play the game with NETGEAR and then worst case pop them in the loft till it gets fixed or eBay them
As per my last post I don’t plan to buy anything else my ZYXEL MUlti X 3 node system was faultless for 2 years so it’s back in only benefit NETGEAR brought me was slightly faster WiFi on some devices and NETGEAR armour
This is a puzzling issue, as I have several (more than 25) RBK753 systems running in router mode, as the only router connected to different ISPs and personal owned modems.
Not one system experiences any DND errors. They all run smooth.
I did have one system, that was connected to WOW network, that had DNS errors that turned out to be, the modem was being directed to West Point Ga servers, when the customer is in Tampa Bay. As soon as WOW reflashed the modem and rerouted to the proper DNS servers, the issue was gone. However, most of the time, my setups are configured to use 3rd party DNS servers, instead of the normal 192.168.1.1 or 192.168.0.1.
I don't have any affiliation with Netgear, other than to use their product. We chose the orbi system because of its speed and reliability. And for the record, their spport is no worse than the competitors.
I agree with Furry. Constantly posting over and over, the dis-satisfaction with the product, and threatening to return it, doesn't help the issue. If you purchase a product and are unhappy with it, return it, sell it, give it away and find something that works for you.
Orbi is not really for novices. There are other user friendly mesh systems on the market, that are more plug and play.
- Then you should login to your router using Telnet and actually see this issue happening right in front of you. As the errors the DNS server/ dsnmasq produce will be right there in the logs (internal). The reason? Because dnsmasq is badly configured - this you can see when you login using Telnet. So there is no way around it. It's factual.
Hence the reason why Netgear did fix this issue for the Orbi Pro. As it's an actual problem affecting everyone.
Netgear should fix the DNS server/ firmware for the Orbi AX.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.
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