Network connection errors
I emailed support and got an unhelpful reply directing me to the help site even though I paid for Nextdns. I don't see why I have to do all this work and troubleshooting for a service I paid for. I have nextdns on my PC and also two android phones. On the phones it is set up via private DNS as instructed. I am also running NordVPN. With Nextdns set on the phones I have random network connection errors. As if connectivity to nextdns drops out. I have been unable to fix it. I did try using Adguard DNS instead to see what happens and everything has been fine. No random network connection errors. Using NordVPN or not. I'd like to understand why this happens with Nextdns as I've proven it is the cause since Adguard doesn't produce the same problem.
2 replies
-
Possibly you are experiencing the same issue as I do. If I'm connected to my home wifi and/or lte everything is fine. But if I connect to work wifi I'm forced to disable my dns as our network security doesn't allow redirects.
-
Honestly, this may be less of a NextDNS issue and more something the app developers need to be aware of directly.
If the application is failing because standard Android Private DNS filtering blocks required backend calls without any graceful handling or fallback behavior, that’s arguably something worth reporting upstream to the app/vendor as well.
A lot of these “network connection errors” end up being:
hard dependencies on telemetry/analytics endpoints
unhandled API failures
missing fallback logic
playback/session initialization tied to Google services
The Android app ecosystem has gotten extremely dependent on cloud-side SDK infrastructure over the years, and sometimes DNS filtering exposes just how tightly coupled some of these apps actually are.
Check out their Contact information here
Content aside
-
1
Likes
- 6 hrs agoLast active
- 2Replies
- 72Views
-
5
Following
