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...
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.
DHCP wouldn't cause DNS errors.
- Yes 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.
This article also includes OpenWRT as specifically vulnerable (the other article mentions Netgear as a manufacturer. I believe Netgear routers (among many) is based on OpenWRT?
https://www.helpnetsecurity.com/2021/01/19/dnsmasq-vulnerabilities/
Note- I don't know if this is THE issue, especially since Netgear has the annoying habit of NOT stating what their updates address. I'm just stating a possible source of the issue.
Anything is possible. However since some users have disabled DST or made a change in NTP, possible that these two could be related. Seems that for the most part the problem appears to be over after these changes, until the next time we have the time change.
Yes Orbi is based off a build of WRT. If you look at the telnet window when you log in, it gives this information.
tak1313 wrote:This article also includes OpenWRT as specifically vulnerable (the other article mentions Netgear as a manufacturer. I believe Netgear routers (among many) is based on OpenWRT?
https://www.helpnetsecurity.com/2021/01/19/dnsmasq-vulnerabilities/
Note- I don't know if this is THE issue, especially since Netgear has the annoying habit of NOT stating what their updates address. I'm just stating a possible source of the issue.
