DNSCrypt Proxy 2 for Android | privacy oriented

A flexible DNS proxy, with support for modern encrypted DNS protocols such as DNSCrypt v2, DNS-over-HTTPS and Anonymized DNSCrypt.

Features

• For all features please refer to the OFFICIAL PAGE
• All binary files are downloaded from the OFFICIAL RELEASE PAGE

Pre-built binaries

Up-to-date, pre-built binaries are available for:

• Android/arm
• Android/arm64
• Android/x86
• Android/x86_64

Differences from the main dnscrypt-proxy project

• server_names = acsacsar-ams-ipv4 [NLD], arvind-io [IND], bcn-dnscrypt [ESP], d0wn-tz-ns1 [TZA], dnscrypt.be [BEL], dnscrypt.ca-1 [CAN], dnscrypt.ca-2 [CAN], dnscrypt.eu-dk [DNK], dnscrypt.eu-nl [NLD], dnscrypt.one [DEU], dnscrypt.pl [POL], dnscrypt.uk-ipv4 [GBR], ev-to [CAN], ev-va [CAN], faelix-ch-ipv4 [CHE], faelix-uk-ipv4 [GBR], ffmuc.net [DEU], jp.tiar.app [JPN], meganerd [NLD], plan9-dns [USA], publicarray-au [AUS], sarpel-dns-istanbul [TUR], scaleway-ams [NLD], scaleway-fr [FRA], serbica [NLD], skyfighter-dns [NLD], v.dnscrypt.uk-ipv4 [GBR], ventricle.us [USA] are the resolvers in use.

• doh_servers = false (disable servers implementing the DNS-over-HTTPS protocol)

• require_dnssec = true (server must support DNSSEC DNS security extensions)

• timeout = 1000 (set DNS query max. response time from 5000 to 1000 ms.)

• blocked_query_response = 'refused' (set refused response to blocked queries)

• dnscrypt_ephemeral_keys = true (create a new, unique key for every single DNS query)

• fallback_resolvers = ['91.239.100.100:53'] (Use UncensoredDNS as fallback resolver instead CloudFlare)

• netprobe_address = '91.239.100.100:53' (Use UncensoredDNS as fallback resolver instead CloudFlare)

• block_ipv6 = true (immediately respond to IPv6-related queries with an empty response)

• blocked_names_file, blocked_ips_file, allowed_names_file and allowed_ips_file options enabled (use the related files, created in your Internal Memory, if you want to filter your content)

• anonymized_dns feature enabled (routes are indirect ways to reach DNSCrypt servers, each resolver has 2 relays assigned)

• skip_incompatible = true (skip resolvers incompatible with anonymization instead of using them directly)

• direct_cert_fallback = false (prevent direct connections through the resolvers for failed certificate retrieved via relay)

Installation

1. Download latest .zip file from dnscrypt-proxy-android | CHANNEL on Telegram and flash it with Magisk Manager.
2. Reboot.
3. Test your DNS: https://dnsleaktest.com/

Configuration (post-installing)

• You can edit dnscrypt-proxy.toml as you wish located on /sdcard/dnscrypt-proxy/dnscrypt-proxy.toml, or /data/media/0/dnscrypt-proxy/dnscrypt-proxy.toml.
• For more detailed configuration please refer to official documentation.
• For more support on a good privacy oriented setup, join with us at dnscrypt-proxy-android | CHAT on Telegram.

AFWall+ users only

If you experience no connection issue after flashing the module I suggest you to insert these scripts: (in both, enter and shutdown boxes)

iptables -A "afwall" -d 127.0.0.1 -p tcp --dport 5354 -j ACCEPT
iptables -A "afwall" -d 127.0.0.1 -p udp --dport 5354 -j ACCEPT

The issue is related to the use of AFWall+ and only happens on some devices, it depends on how the DNS configuration is implemented in the device itself.

Changelog

Full changelog

Credits

• DNSCrypt-Proxy2 upstream | jedisct1
• bluemeda for the original module
• All contributors