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...
I don’t think it is a hardware issue. I have changed my device twice from Costco with same issues. Unfortunately NG support did not do anything either. My ticket is open for multiple weeks and now received an email that they want to close the ticket due to no activity on ticket :-(. I just changed dns to static at device level.
Ace321 wrote:
I don’t think it is a hardware issue. I have changed my device twice from Costco with same issues. Unfortunately NG support did not do anything either. My ticket is open for multiple weeks and now received an email that they want to close the ticket due to no activity on ticket :-(. I just changed dns to static at device level.
I agree, DNS resolution is a feature which hasn't changed in years and I can't imagine that hardware is the source of the problem. When dealing with NG support, you have to reply to them even if just to say "I already tried that" otherwise they will close the ticket. So go ahead and reply back to keep it alive. Those of us with support left on these devices (it's not free forever) should keep our tickets open and keep trying the things support suggests--this lets us exhaust all of the options they can think of AND THEN they will need to investigate further. Without doing this we just won't get enough attention on the problem.
While it's true that setting static DNS on every device in the home is a valid work-around, 1) it still does not provide a seamless experience for those WANTING the same OpenDNS support throughout the home, and 2) it's a huge pain to go and manage that on every device when you have multiple PC's, laptops, iPads, etc.
Yes for users with in warranty periods with NG, please keep in contact with NG support. I believe there are a couple of different things are are causing this, FW and FW app(Armor), Different ISP and or ISP HW configurations and IPv6. Seems like there has been some common posts in regards to ISP and IPS configurations and some IPv6 involvement. I would say that some have posted about Armor as well.
I for one have not see this issue what so ever, however I don't use Armor or IPv6 so those are disabled. My ISP doesn't support native IPv6. Two modems I have tested Orbi AX out on a CABLE ISP service, Sparklight, CM2000 and CAX80 has not reproduce this issue. I have been wanting to put my CM1200 back online and may soon. So with this configuration and ISP service at least, has not rendered this problem since getting the Orbi AX last year. So from this kind of configuration and ISP service, FW seems ok.
So IMO, leads me to think that there maybe a difference in ISP service experiences with Orbi AX, and since I don't have FIOS or ONT or some different ISP hardware, there maybe issues seen between this level and Orbi AX.
Some of you have mentioned using Armor which has been known to cause problems since Orbi AC days so this maybe another item which NG needs to look into as well.
FURRYe38 wrote:Yes for users with in warranty periods with NG, please keep in contact with NG support. I believe there are a couple of different things are are causing this, FW and FW app(Armor), Different ISP and or ISP HW configurations and IPv6. Seems like there has been some common posts in regards to ISP and IPS configurations and some IPv6 involvement. I would say that some have posted about Armor as well.
As for myself, I am using Comcast cable and Arris SB8200 cable modem, and I am not using IPv6. Also Armor is not turned on/enabled. So just to clarify there are users like me not using IPv6 nor Armor and still experiencing this. Totaly agree to keep in contact with support, it's our only change to get attention on this issue.
Why I think in some cases this is a ISP and Orbi issue as well. Seen lots of posts of problems with users on CC and Cox.
Ya, Hopefully NG can get this figured out. Definately share your debug logs with NG support. You can enable them under router IP address/debug.htm. Keep this running and when the problem happens, capture the logs and send to NG.One thing that some of you maybe able to do, if you still have a prior router, re-install that router, disable the wifi radios on the router, then configure the Orbi AX for AP mode and test. Would be helpful for NG to know the results of this as well.
