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 + Circle frequent DNS failures
I've spent the better part of the past two weeks troubleshooting some DNS issues. They are similar to those reported recently here and probably here and related to similar reports as long as a year ...
I've already given up trying to get Orbi to function as a proper Router + Disney + Armor, because it's nothing but trouble. To get Orbi to a stable state, I have to disable practically everything that I could disable, including its internal DNS and DHCP client. I'm currently keeping Orbi for its WiFi capability and delegate all other router functions to DIY pfSense Router Firewall.
I went through a similar pain before I settled on the current setup, which has been holding up quite well during Stay-At-Home order.
- SB8200 -> pfSense -> Orbi AP Mode with static DNS servers and IP address
I settled on pfSense because I need a reliable Gigabit Router with enterprise class DNS resolver, DHCP, Firewall, DNS Filtering, VPN, plus a whole bunch of other features that I don't really need. If you're comfortable with installing pfSense, it's worth a shot.
Shahab, I shared your frustration because I had been through that rollercoaster rides. If you have an old router lying around, dust it off and switch Orbi to AP mode, decouple Orbi from routing chores. You could switch it back once this lockdown/COVID-19 ordeal is over.
So by shutting off Circle and setting the DNS to 1.1.1.1 and 8.8.8.8, up time for the Orbi router has been nearly 95%, with the remaining 5% a combo of things I could think of other reasons for the issue, .ie changes I may have made on the router setup.
I am having a strange issue in that my chrome browsers largely on Windows 10 devices are failing to recognize a site and give me an illegal name error (clearly a DNS issues), but a reload of the page will send me back to where I was navigating. This includes chrome on my Samsung phone.
Strangely, the computers that are setup where the DNS is set to my pi-hole have not given me this issue.
I don't know what to think. I was going to install Vexel's firmware, but I'll take the 95% uptime over unknown issues anyday, at least in these times where I have 5 family members screaming if the "stupid wi-fi sucks" is down.
You might try Voxels FW. It's stable and I have not seen any DNS issues on his FW. Ever.
Someting to consider.
At least your system seems working better now.
Smge1lc wrote:So by shutting off Circle and setting the DNS to 1.1.1.1 and 8.8.8.8, up time for the Orbi router has been nearly 95%, with the remaining 5% a combo of things I could think of other reasons for the issue, .ie changes I may have made on the router setup.
I am having a strange issue in that my chrome browsers largely on Windows 10 devices are failing to recognize a site and give me an illegal name error (clearly a DNS issues), but a reload of the page will send me back to where I was navigating. This includes chrome on my Samsung phone.
Strangely, the computers that are setup where the DNS is set to my pi-hole have not given me this issue.
I don't know what to think. I was going to install Vexel's firmware, but I'll take the 95% uptime over unknown issues anyday, at least in these times where I have 5 family members screaming if the "stupid wi-fi sucks" is down.
- The lockup is an underlying problem with dnsmasq, which freezes under high load, not perticularly the Orbi or Circle per se.
The problem here is that using Circle forces all DNS through dnsmasq, increasing the load. Any solution redirecting a lot of DNS traffic away from dnsmasq on the Orbi helps.
The problem with the firmware is that it fails to recognize the problem and self-heal. Easier to point fingers.
Ultimately getting DNS off the Orbi onto an upstream router or firewall or external DNS resolver like the circle hardware or a PiHole, should work. Have you tried Voxels FW by chance yet?
dbwiddis wrote:
The lockup is an underlying problem with dnsmasq, which freezes under high load, not perticularly the Orbi or Circle per se.
The problem here is that using Circle forces all DNS through dnsmasq, increasing the load. Any solution redirecting a lot of DNS traffic away from dnsmasq on the Orbi helps.
The problem with the firmware is that it fails to recognize the problem and self-heal. Easier to point fingers.
Ultimately getting DNS off the Orbi onto an upstream router or firewall or external DNS resolver like the circle hardware or a PiHole, should work.
