NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi (RBR50) DNS keeps failing.
Hi, I'm have an RBR50 running Firmware V2.7.2.104 that has been working fine for a couple years now. Very recently, devices connected to the Orbi have started getting failed DNS queries, causing th...
Ran into this issue as well. This Reddit thread has the best workaround I've found for the bug(s) that Netgear pushed out with its most recent release for this model.
https://www.reddit.com/r/orbi/comments/m5l3vk/orbi_dropping_dns/
There are several options. I think the best one is to use the debug.htm page to enable telnet, log in, and modify the DHCP settings to tell clients to contact external DNS servers directly thus bypassing the failing proxy on the router. This change sticks until the router is rebooted which is rare for me. All devices will renew theri DHCP lease within 24 hours (or less) to get the new setting. I recommend forcing devices to renew their DHCP lease to get the new settings sooner. You can unplug the LAN connection, toggle wifi on/off, reboot a device, or issue the command to renew specific to your device/OS. However if you have one computer plugged directly into a LAN port, one simpler way to reset all the wifi attached device's DNS config is to change the wifi name configured on the Orbi, wait a few minutes, and then change it back. I judged "a few minutes" by monitoring my phone to see when it decided the wifi connection was lost. Once back to the original name, my (Android) phone took a couple of minutes to accept the wifi was stable.
There are also reports that the bug is an interaction issue between the DNS process (dnsmasq) and the traffic measuring/metering feature, and that disabling the traffic measuring feature will avoid the bug. Since I don't *need* the measuring feature, I disabled it just in case a thunderstorm glitches the power, there's a chance the Orbi will remain reliable afterwards without the effort/distraction of the reconfiguration workaround.
Apart from the semantic issue of the meaning of "solution", it appears to me that lukedude is reporting a DNS issue with an RBR850, not an RBR50. (Post #30)
No previous RBR50 firmware will install on an RBR850.
I do not recall seeing posts that the RBR850 was subject to the iidentical Traffic Meter/Daylight Saving Time issue as the RBR50.
But then, I do not read the AX forum because I do not have one.
I continue to suggest that creating a new post in the AX forum is the most expeditious way to address this issue.
Could be. I got involved in this because of my RBR50 and posted in a stream for that.
Either way, I suspect the same solution will work for his mode except that he'll have to look for the proper earlier firmware download under his model on the Netgear site. Even so, thanks for pointing that out.
It will be good when Netgear fixes this and people aren't in a frenzy to get their systems working. Most folks don't want to deal with this stuff, I think. They just want their systems to work so they can do business. Indeed, I'd say that most see this as Netgear's responsibility since they're the vendor of the gadgets. We are purchasers.
Thanks for the attempt but 9 months is far too long for this issue to have been active. I returned my orbi to Amazon.
Sorry to hear that it didn't work out for you. There are many manufacturers of routers out there. I'm sure you'll find one that does what you need without the aggravation.
Wil
You can try Voxels FW for Orbi:
https://community.netgear.com/t5/Orbi/Voxels-FW-available-for-50-series-Orbi-only-available/m-p/1883615#
You can revert back to stock FW if it doesn't work out for you.
You might try the offered beta FW version mentioned in the link provided the early post.
WillRXR wrote:Could be. I got involved in this because of my RBR50 and posted in a stream for that.
Either way, I suspect the same solution will work for his mode except that he'll have to look for the proper earlier firmware download under his model on the Netgear site. Even so, thanks for pointing that out.
It will be good when Netgear fixes this and people aren't in a frenzy to get their systems working. Most folks don't want to deal with this stuff, I think. They just want their systems to work so they can do business. Indeed, I'd say that most see this as Netgear's responsibility since they're the vendor of the gadgets. We are purchasers.
