DNS broken after upgrade to 4.9.0

will.qiu · June 1, 2026, 4:17am

We sincerely apologize for the inconvenience caused.

The only change we made remotely was adjusting the following AdGuard Home setting. This modification should not affect the normal operation of other router functions, and it has been tested and verified both locally and by other users.

Issues with enabled Wireguard Client connection and AdGuard

Please try SSH-ing into the router and run the following commands to force AdGuard Home to send DNS queries through the WAN only:
sed -i 's/explict_vpn/nonevpn/g' /etc/init.d/adguardhome
/etc/init.d/adguardhome restart

# To restore:
cp -r /rom/etc/init.d/adguardhome /etc/init.d/adguardhome
/etc/init.d/adguard

As shown in the screenshots we provided, when we finished the remote session, the router was still connected to the internet normally and had successfully restored connectivity to the AdGuard Home upstream DNS servers, the opkg repositories, and DDNS services after making change.

Could you please clarify the following?

Did you discover the issue as soon as you returned home?
What was the status of the router's LED indicators when the issue occurred?
Was the device still shown as online in GoodCloud at that time?
What exactly happened when devices could not connect to Wi-Fi? Were they unable to connect at all, able to connect but unable to obtain an IP address, or able to connect but unable to access the internet?
Did rebooting the router restore normal operation?