I updated to Release 5 today and started having issues with encrypted DNS over TLS. I was using NextDNS, but no matter which provider I select, it seems to be using Cloudflare, and it wasn’t working in my setup.
The only way I could get DNS working again was to switch back to manual DNS and enter the server addresses manually.
Is anyone else seeing this behavior after upgrading to Release 5?
There was a similar error in 4.8.4 when first launched, it could not resolve hostnames so dns over tls or https didn’t work.
I’m using AdGuard Home, but only as a way to point everything to NextDNS, by using NextDNS as the upstream server, I’m not actually using it for filtering.
Everything works perfectly on Beta 4, so I’m hesitant to upgrade. Are you using AdGuard as well?
I am not using Adguard Home. Last night I ended up going back to Beta1. I was running into several domains that were not resolving. I was unable to ping them either, and then randomly they would start working and then fail again. No issues after reverting to Beta1. I’ve been on Beta1 since around 4/17.
NextDNS has a client for routers ( GitHub - nextdns/nextdns: NextDNS CLI client (DoH Proxy) · GitHub ) you could use. I’m using ControlD with their ctrld utility on my Flint 3, circumventing the built in Encrypted DNS feature, bet the NextDNS one probably works pretty much the same.
Sorry but where do you see beta 5 written on the screen?
When you download the firmware, it’s titled with the release.
be9300-4.9.0_release5-1022-0515-1778843436.bin
Hi,
We tested locally using the BE9300 v4.9.0 release 5 firmware but were unable to reproduce the issue.
Please SSH into the router and run the following commands to check:
# Check the current firmware release version
# If the result shows release 4, please re-download the latest beta firmware from the download center and upgrade again
cat /etc/glversion
cat /etc/version.type
# Check the DNS server currently in use
grep server /var/etc/dnsmasq.conf*
# Adjust according to the result above, but it should normally be 5453
netstat -anpl | grep 5453
# If you are using a paid NextDNS service, please mask the ID before sharing
cat /etc/dnsproxy/dnsproxy.yaml
I’ll have to redownload and retest on Saturday. I’ll post my findings. Thanks
I noticed that Release 5 was moved out of Beta, though it appeared to use the same BIN file. After updating my Flint 3, I was still experiencing the NextDNS issue, but I was able to resolve it by changing the NextDNS ID, saving the setting, then switching it back to the desired ID and saving again. Everything is working properly now.
Thank you for the update.
Yes, it seems that the DNS settings from v4.9.0 beta1 could not be properly retained after upgrading to v4.9.0 release 5, even though the WebUI still displayed them correctly.
And reconfiguring the DNS settings should resolve the issue.
In any case, we’re glad to hear that everything is now working properly.