I understand the “Private DNS” function in /e/ is based on DoT (DNS over TLS).
Given DoT can be easily blocked by network administrators or service providers (it runs on a dedicated port), I am wondering why the /e/OS team didn’t chose DNSCrypt instead, and whether there are any plans of offering DNSCrypt functions baked into the /e/OS.
I see there is an older post (DNSCrypt on /e/ - #3 by marcdw) which talks about app-based DNSCrypt implementations and I know DNSCrypt is supported for Android OSes, so wondering what are the development team’s plans (if any) in this direction.
To be fair, the /e/OS team didn’t choose anything. Private DNS was introduced with Android 9 Pie with DoT being the ‘protocol’ of choice (which works system-wide unlike DoH). That’s a Google choice. Every version since then has it.
I don’t think even the the most privacy/security/deGoogly focused offerings have made any attempt to make changes in that area. And of course they are all based on an upstream (like LineageOS) to which various changes are made but making changes to Private DNS code is probably not trivial.
Also DNSCrypt has some configurations to consider. Being able to use any number of servers (InviZible Pro, f.i., will choose the server with lowest latency), anonymous relays (for servers that support it), and more. With Private DNS you select or add a single server and done. DNSCrypt really wouldn’t work out in that limited setting.
Using DNSCrypt via third party tools (InviZible Pro, a Magisk module, RethinkDNS, etc.) is the only way it seems.