Okay, I've had the RT-BE92U for a few months, and it was fine initially. I switched ISPs a few weeks back, and about the same time I upgraded the firmware to the latest available at that time. Man... it's been stupid since that time. The issues initially seemed to start with WiFi clients suddently all dropping off once a day or so, requiring the router to be restarted. This was the case for a couple weeks, until a new FW version came out (the latest to date) which I quick applied, hoping it would resolve my issues.
Much to my dismay, it made things worse. Now I was dropping WiFi connections up to 2 times a day. I began troubleshooting from a wired computer, running my logs through CoPilot searching for clues. 2.4Ghz was over utilized is what the consensus was, so I began tuning WiFi settings in hopes of reducing the utilization, which did seem to help some, but not enough. Then 3-4 days ago, things got really bad. Devices have been dropping every 2-3 hours, including wired devices. My family is fuming. I could no longer access the router through a wired connection, and I would have to power cycle the router to get things working again. Something is wreaking havoc with this thing.
Tonight, I finally had some time, so I did a factory reset and rebuilt from scratch. This time, only setting up one main WiFi network, and an IoT network. Everything else I basically left largely untouched. Once I got the basics configured I bagan testing and immediately discovered that I couldn't access any websites. I quickly discovered that DNS queries from the clients were failing. I double-checked my router WAN settings and confirmed that I was set to simply use the ISP DNS servers. I tried a couple of the other built-in DNS server configurations, and even tried manually pointing to various public DNS IPs. No change. Nslookups from the router itself are working fine, however. Go figure.
However, I manually set one of my clients to use 8.8.8.8 and DNS queries were successful. The same was true when I set the DNS server to an internal PiHole server I had on the network, but was not currently utilizing. I tried pointing the router to 8.8.8.8, 1.1.1.1, or adguard, but each configuration would result in the same result of DNS lookups failing on the clients.
I then set the DHCP server on the router to advertise my PiHole server for DNS and this worked.
So what the heck is up with this router that it won't even pass DNS queries properly to the clients? I haven't had it running long enough with this config to see if that might resolve my dropped client issue or not. I'll see how the next 72 hours ago. If it does, then my hunch is that this things is choking on passing DNS queries, and eventually just dies from the overload of pending queries. I spent too much money on this thing to have such horrible issues.
