Private DNS (DoT) on Embedded / IOT Android Devices - Help With Connection Errors

Good evening, everyone. I was wondering if any of my fellow Tilders had experience with using Android's Private DNS feature on unconventional android devices e.g. WearOS, Android TVs etc.

It was quite easy to figure out exactly how to set up an alternative DNS server on these devices. By default, Google has hidden the private DNS setting on them, but it is still accessible from ADB. In both of my examples it is likely easiest to enable “Wireless Debugging”, pair the devices successfully, and then run the commands.

settings put global private_dns_specifier one.one.one.one (replace this with the pertinent server!!)
settings put global private_dns_mode hostname

The issue I have been running into, however, is if there is seemingly any form of content filtering enabled on the DNS server of your choice, the WearOS device seems to think internet is unavailable when first connecting. If you open the Settings app and leave it open for long enough on the Wi-Fi page, it will switch from “Internet not available” to “Connected”. Contrary to this, if you open an app like Samsung Internet for, it does not take this time and just refuses to use any configured Wi-Fi network.

To go into my specific situation in a little more detail, I use NextDNS configured with Hagezi Multi PRO++ block list. I have no issues on my S24+ with regard to internet being deemed unavailable by the OS (sure the occasional public Wi-Fi network blocks DoT—I just use mobile data then). I have also yet to try it on my Smart TV, which is frankly the more important target device than my watch (I will get around to it in the new year once the holidays are over).

This is all a potentially very convoluted way to ask what people's experiences are with this, and if they have faced similar problems to me when using providers like NextDNS, AdGuard etc. that provide content filtering options on their encrypted DNS connections.

Merci beaucoup !