Crazy. Whatever it was the update to 3.0.0.4.386_47027 seems to have fixed it. I once again get name resolution on hosts I don't manually register via "hostname (Optional)". I don't know what it was but seems like it's back to normal now. Thanks all!
Sorry it's kind of confusing I suppose. The issue seems to be how the ASUS UI generates the static DNSMASQ config during boot changed. I'm just applying the new firmware today to compare. The host definitions haven't been getting their client name as a default hostname.
Interesting. Stock is on 2.84 it seems. I can't find any release notes or changelogs for 45130
It doesn't seem related to dnsmasq as much as the ASUS UI config of it. I can easily edit dnsmasq.conf or dnsmasq add in jffs to manually assign hostnames like usual. It just seems the ASUS...
Thanks for the responses. The model is an AX89X that has been working fine for about a year now. I do have auto updates on and haven't knowingly rebooted it for a while. Connections started acting kind of funky so I rebooted it yesterday.
I've also converted the trusty AC68U I replaced into an...
Hi - longtime ASUS user and I've been running fine for years but suddenly after a reboot all of my local host resolution began to fail. I've held off on Merlin with this one and currently on stock 3.0.0.4.386_45130. I think the update may have come in automatically since my last reboot and it...