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...
msinex wrote:I've reached the end of my rope with this DNS issue. I love the performance of the router outside of the DNS issue, and since I can't return it I'm thinking the best route forward is to throw it in AP mode and put another router in. That seems utterly ridculous in my mind to solve such a basic glaring error, but I feel it's cost effective to at least give it a try.
It sounds like others have gone down this route. Can you provide what router you used that behaved well with the Orbi? I'm not looking for something super complex, just stable and won't impact the speed. Would like to avoid Netgear products for that for obvious reasons. Thanks for the help!
I've been using my trusty Asus RT-AC68U, which is what i used before going mesh (yes, I know Asus has AiMesh, but wanted to try something different).
It's been working great - all the features and controls that Orbi lacks (QOS) or wants to rip people off for (Armor/parental controls), without the DNS issues that apparently Netgear's coders are not capable of/don't have the skill to fix.
I change routers every few years anyway, even if there's nothing wrong. In the switch from Asus, as stated earlier, I wanted to try mesh because I was using a TP-Link extender with the Asus for a certain part of my house.
So in a few years, when it's time to try something new, it won't be Netgear. Too bad, I USED to use Netgear stuff many years ago ala the WNDR4500 and was completely satisfied with it, which is why I gave Orbi a shot.
msinex wrote:Thanks tak1313 , do you use it in combination with the Orbi mesh in AP mode?
Yes - 68U as the router > Orbi in AP mode connected to the LAN port of the Asus (wireless backhaul to the satellite).
The one disadvantage if you're the type to contantly looks at what's connected to the satellite versus main router signal is that you have to log in to Orbi's page to see - the list of connected devices on the router (Asus in this case) will always show all devices as a wired connection.
My service is only 100mpbs so the Asus does not introduce any speed issue, but if you have a gig service, you may want a router with a bigger WAN input (2.5gbe, etc.), or you won't get TRUE gig service out of the LAN ports - though most people wouldn't even notice, because the NEED for TRUE gig service tends to be in the mind for most consumer users.
I don't remember what thread I posted my OPINION in, but my OPINION is that Netgear's coders don't have the skill/can't fix the DNS issue because I THINK they fiddle with dnsmasque to do data harvesting of IPs users visit (rather than using the vanilla/raw dnsmasque). They can't figure out a way to make dnsmasque work properly AND have their data harvesting cake too.
Forgot to mention - turn off the router's wifi/radios since you're using Orbi for wifi. Also, I use the LAN ports of the Asus for the three things I keep wired (two Synology's and a printer) - the fourth LAN port being used for the Orbi.