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
Jul 27, 2020Apprentice
Thanks for the reply FURRYe38 , my ISP is spectrum and the modem is a Spectrum branded with model e31u2v1. This link shows the picture and an overview from someone else - https://larrytalkstech.com/the-spectrum-mystery-modem-e31_2v1/
FURRYe38
Jul 27, 2020Guru
Some DNS issues come from the ISP side. I would make contact with the ISP to see if they are noticing anything. Make changes on the Orbi RBR for custom DNS addresses as well to see if this changes anything.
I don't see any DNS issues with mine however I'm on a different ISP and use a different modem.
- msinexJul 28, 2020Apprentice
Thanks FURRYe38 , I actually shifted back to my old Nighthawk to see if it was something with my ISP or my network setup, and I didn't see any of the same DNS errors (just much less WiFi coverage). I also wanted to get it back up and running and using as similar a router build as possible for the Orbi. I did that, and am still having the same DNS issues (and now the dropped wifi issues). Thanks for the thought though!
- FURRYe38Jul 28, 2020Guru
Has a factory reset been performed since apply v32?
What CTS values are you using under Advanced Tab/Advanced Settings/Wireless Settings
Do you have Armor enabled?
msinex wrote:Thanks FURRYe38 , I actually shifted back to my old Nighthawk to see if it was something with my ISP or my network setup, and I didn't see any of the same DNS errors (just much less WiFi coverage). I also wanted to get it back up and running and using as similar a router build as possible for the Orbi. I did that, and am still having the same DNS issues (and now the dropped wifi issues). Thanks for the thought though!
- msinexJul 28, 2020Apprentice
Thanks FURRYe38 . I have done a factory reset since I ran into the issue, and it didn't resolve the situation. I believe it may have been before the latest firmware update though. Was there something in that update that may have addressed this issue?
I haven't ever enabled Armour on the device (or the Disney circle then either, which seems to cause issues from what I have seen trying to diagnose this myself reading past forum posts).
On CTS, everything is enabled on that page and automatic is turned on. There is a greyed out value number of 2347 for the threshold. I haven't done any research on these settings in the past, should I?
- arlomikeJul 27, 2020Apprentice
Sound like you might have an IP conflict and should look into that. I've noticed that the DHCP server is dumb and hands out conflicting IPs.
- msinexJul 28, 2020Apprentice
Thanks arlomike , could the DHCP be causing the wifi dropping off for my mobile devices?
- arlomikeJul 28, 2020Apprentice
msinex wrote:Thanks arlomike , could the DHCP be causing the wifi dropping off for my mobile devices?
If wifi is disconnecting, then it's not DHCP. If you are connected to your wifi SSID and you have intermittent connectivity to sites, etc., it is possible there is a IP conflict possibily due to DHCP handing out a conflicting IP. Best way to check is to login to the router and see if your IP assignment conflicts w/ other devices that has gotten a lease from the DHCP server. I ran into this problem w/ my wife's phone. Her phone and my iPad had the same IP address. These devices got their IPs via DHCP. A work around is to statically assign your device that is not within the DHCP range.
- FURRYe38Jul 27, 2020Guru
DHCP wouldn't cause DNS errors.
- jimmyandrewsMar 19, 2021AspirantYes it could actually. When netgear doesn't follow international technical guidelines for dchp, as they do in many of their products, for instance, not honoring dns settings and forwarding the router as the dns as netgear does. It's supposed to carry over the dns that is set. So, the dns resolver cache gets full, doesn't clear, and the arp tables routes to bad or stale addresses.