DNS only working via DHCP

[eagctx]

I have a new RT-BE92U. I'm basically replacing a RT-AX86U and moving that to an IoT only subnet.

NB. These are both in AP mode. They are not "routers".

Anyway, ran into an issue with DNS. Trying to setup the 92U the same as the 86U, manually setting the LAN IP address, and DNS works fine and has for years on the 86U. Doing that on the 92U and DNS does not work. I spent quite a bit of time to discover that letting DHCP assign an address AND DNS, works. Even thought they are the same addresses/settings as the static ones.

Anyone have any ideas?

 

[jzchen]

The only thing I can think of is you may have accidentally assigned a repeat IP address to the BE92U that a different network client also has.

 

[eagctx]

Yeah, I double checked that so I wasn't making a rookie mistake.

I need to circle back on this at some point. Right now there are bigger issues with this router rebooting every 30 min.

 

[dave14305]

How are you testing this? If you’re getting the same IP in both cases, you need to look at how the AP is populating the /etc/resolv.conf file and whether the IPs within are pingable from the AP.

 

[eagctx]

I'm going to pin this on the RT-BE92U. I returned it because of this and many other issues.