Private DNS server cannot be accessed when switching to Mobile (Bell Canada)
I have a Samsung S24 Ultra (this same thing was happening on my S23 Ultra as well). It is setup with Private DNS (netid.dns.nextdns.io). I've also tried with a hostname at the start (phone.netid.nextdns.io). I"m on Bell Mobility in Canda.
Quite often when I leave the house (mind you, it's not every time) I will find after a while that the connection isn't working. No site will come up, mail not received, no notifications. Upon investigation, the private DNS will read "Private DNS server cannot be access". If I flip it to automatic or none, it will immediately start working again. And when I flip it back to Private DNS, it will continue working.
I can't seem to nail down why this is happening.
A friend, same phone, also with NextDNS has no problems. The only thing I can find different in our setups is he's on a different cellular provider.
Not sure what to try next to troubleshoot.
25 replies
-
Well, going on what you’ve said it’s most likely to be your cellular network provider that’s at fault. Seeing as you mentioned your friend with same setup on a different network works ok.
-
Confirming the same issue with AT&T in the USA. Using the same setup with Android Private DNS DoT NextDNS setup.
-
Quick update.
I switched over to ControlD. Having, overall, far less problems than with nextdns.No problems on the android, and my local network is much happier too.
-
I tried just doing Android Private DNS with Quad 9 (over TLS) and I still got the Private DNS Server Cannot Be Accessed error. It can't be a NextDNS problem if multiple endpoints are throwing the same error. It has to be an Android/Samsung specific issue. Just my thoughts...
-
I'm having similar issues on two different devices (s24 plus and s10 plus), except this happens even without switching networks. Only happens on wifi after being connected for a while- mobile data works constantly. Turning off NextDNS or switching to data and back to wifi resolves the issue instantly. My S10 Plus used to be my daily device and it works well until now, so something on NextDNS' end is messed up from my guess.
-
This is gonna sound weird, I'm from Control D and we've been troubleshooting this exact issue... except in reverse where people say this happens with Control D, and when they switch to NextDNS the problem goes away.
Wanna colab on the troubleshooting? We've spent days on this and can't seem to figure out the cause except that it somehow relates to CGNAT on some cell networks.Using DOH (via app) solves the issue too.
Content aside
-
3
Likes
- 1 mth agoLast active
- 25Replies
- 566Views
-
7
Following