FYI: Firmware update 2.5.1.8 causes DNS timeouts only fixed by reboot on my RBR50 and RBS50's

What happens if you don't use any custome DNS on the RBR? 

Try using 1.1.1.1 and 9.9.9.9 for DNS.

Has a factory reset and setup from scratch been performed since last FW update? 

I and others don't see this issue. Doesn't mean that this version is buggy either. Try a reset next time you update FW to be sure. 

If it was FW, more users would be posting about it. 

---

perfarny wrote:

Hi All,

Mostly an FYI as I've downgraded back to 2.3.5.30 and all is well again.

 

I have one RBR50 and three RBS50's that have been working flawlessly for pretty much as long as I can remember behind an Xfinity Xfi modem that is bridged. I saw the firmware update 3 days ago and upgraded all devices to 2.5.1.8.  Ever since, the RBR50 has gone unresponsive for DNS queries multiple times per day. Existing connections were fine (i.e. it passed traffic back and forth just fine) but as soon as name resolution came in (i.e. going to a new website) the connection would fail with a DNS timeout. The only way to fix it was to reboot the RBR50.

 

To troubleshoot, I noted the DNS server it is setup to use (comcast 75.75.75.75 and .76) and at a time when name resolution wasn't working, I manually configured my desktop to use those DNS servers while leaving IP at DHCP. Voila, everything worked fine. So, for whatever reason, while the RBR technically had access to the DNS server (since I could connect to it from my desktop) it was timing out queries.

 

I downgraded all devices back to 2.3.5.30 and everything has been working again for the last 24 hours. Note also that for as long as I've had these devices (2+ years) the network map shows all satellites connected directly to the router. After the 2.5.1.8 update, it showed that 2 of the satellites were connecting to one of the other satellites, and that one was the only one connecting to the router. I know it's a mesh, but a bit odd that after all this time the topology suddenly changed.

 

Anyway - as noted, mostly an FYI. Curious how these issues get back to the dev team when the free 90 day support has long expired?

 

Thanks,

Per

---