Android: DNS-over-TLS/QUIC stops working when switching from wifi to mobile network
I've been using NextDNS for quite some time and all has been working as intended, but recently I started experiencing the issue that everytime I:
Switch from wifi -> mobile network results in the device (s23 ultra) being unable to access internet, sometimes it resolves itself after +1 minutes and sometimes I need to disable and enable the private DNS for it to work again. Jumping back to wifi results in the device being able to access internet again.
When using Cloudflares DNS and switching between wifi and mobilen network without any issues every time.
Does anyone have any idea what might be wrong?
Cheers,
6 replies
-
It seems to not always work to disable and reenable the private DNS either, so the only reliable way to have mobile network working as intended is to keep NextDNS disabled when not on wifi which sucks
-
Bumping this, still experiencing the same issues. Anyone have any idea?
-
Thanks for the reply!
The weird thing is that I've now tried out Control D instead for a week and it is working without any hiccups.
I really like NextDNS but if this cannot be solved then I think that I will simply have to move over to Control D (and I would like to avoid using any extra app, I currently have a custom quick setting tile that I created with the help of Tasker that quickly enable/disable whatever dns I have set)
-
What is your router brand & model?
-
I contacted the support service of my router and the response was as follows;
“If any secure DNS is configured in the operating system of the router device, the DNS-related operations of a client switching from a cellular network to a Wi-Fi network are completely managed by the operating system of the router device, except that any other DNS-related request from the client is blocked for security reasons.”
My suggestion to this answer was as follows;
“In the KeeneticOS operating system, we should be able to define exceptions for IPv4 DNS, IPv6 DNS, DNS over HTTPS, DNS over TLS and DNS over QUIC addresses requested by the client. Or it should be able to do them automatically. If the connecting client has a connection that matches the configuration, it should allow this.”
They added
“We have forwarded your request to our relevant departments for evaluation, development requests go through many evaluation stages and if there is no software or hardware restriction and your development request is deemed appropriate, it will be queued for processing, we recommend that you follow the release notes published in this process.”
I also contacted the support service for my smartphone and told them;
I also contacted the manufacturer of the device and requested them to add this feature, since there is no method to provide this automatically on the client side. I explained that on the client using Android 13 and above software, when the “Wi-Fi Enabled” condition is provided via “Modes and Routines”, the “Private DNS” configuration should switch to “Automatic” and when it returns to the cellular network, the defined “Private DNS” should become active. This feature is not currently available. I am in discussions with them as well.
In this case I have contacted the router, the smartphone and the support of the DNS service. I still haven't found the solution.
I guess we are facing incompatibilities because it is a new technology that has just become widespread. Does anyone have a third party solution?
Content aside
- yesterdayLast active
- 6Replies
- 203Views
-
3
Following