Releases: d3cim/dnscrypt-proxy-android
Releases · d3cim/dnscrypt-proxy-android
dnscrypt-proxy-android v2.1.5
Upstream
- dnscrypt-proxy can be compiled with Go 1.21.0+
- Responses to blocked queries now include extended error codes
- Reliability of connections using HTTP/3 has been improved
- New configuration directive:
tls_key_log_file
. When defined, this
is the path to a file where TLS secret keys will be written to, so
that DoH traffic can be locally inspected.
Changed
- Optimized relays.
Removed
altername
resolver (temporarily down).dct-de1
resolver (ceased).dns.watch
resolver (unresponsive).starrydns
resolver (ceased).
Full Changelog: 2.1.4...2.1.5
dnscrypt-proxy-android v2.1.4
Upstream
- Fixes a regression from version 2.1.3: when cloaking was enabled,
blocked responses were returned for records that were not A/AAAA/PTR
even for names that were not in the cloaked list.
Added
dct-ru1
resolver (DNSCrypt | IPv4 only | Non-logging | Non-filtering | DNSSEC | Moscow, Russia).
Full Changelog: 2.1.3...2.1.4
dnscrypt-proxy-android v2.1.3
Upstream
- DNS-over-HTTP/3 (QUIC) should be more reliable. In particular,
version 2.1.2 required another (non-QUIC) resolver to be present for
bootstrapping, or the resolver's IP address to be present in the
stamp. This is not the case any more. - dnscrypt-proxy is now compatible with Go 1.20+
- Commands (-check, -show-certs, -list, -list-all) now ignore log
files and directly output the result to the standard output. - The
cert_ignore_timestamp
configuration switch is now documented.
It allows ignoring timestamps for DNSCrypt certificate verification,
until a first server is available. This should only be used on devices
that don't have any ways to set the clock before DNS service is up.
However, a safer alternative remains to use an NTP server with a fixed
IP address (such as time.google.com), configured in the captive portals
file. - Cloaking: when a name is cloaked, unsupported record types now
return a blocked response rather than the actual records. - systemd: report Ready earlier as dnscrypt-proxy can itself manage
retries for updates/refreshes.
Added
- Script in
customize.sh
file for automatically disable Private DNS feature. dct-nl1
resolver (DNSCrypt | IPv4 only | Non-logging | Non-filtering | DNSSEC | Naaldwijk, Netherlands).openinternet
resolver (DNSCrypt resolver colocated at Sonic.net in Santa Rosa, CA in the United States. No log, no filter, DNSSEC. Provided by https://openinternet.io).
Changed
- Optimized relays.
Removed
acsacsar-ams-ipv4
resolver (unresponsive).dct-ru1
resolver (unresponsive).dnscrypt.eu-nl
resolver (ceased).dotya.ml
resolver (unresponsive).resolver4.dns.openinternet.io
resolver (changed).sgp-dn53
resolver (unresponsive).
Full Changelog: 2.1.2.4...2.1.3
dnscrypt-proxy-android v2.1.2.4
Added
- Automatic redirections in
post-fs-data.sh
file.
Changed
- Use a more modern DNS.SB as
bootstrap_resolvers
.
New Contributors
- @jahway603 made their first contribution in #2
Full Changelog: 2.1.2.3...2.1.2.4
dnscrypt-proxy-android v2.1.2.3
Changed
Full Changelog: 2.1.2.2...2.1.2.3
dnscrypt-proxy-android v2.1.2.2
Fixed
- Forgotten scripts in
post-fs-data
file (it prevent using bootstrap resolvers correctly).
Full Changelog: 2.1.2.1...2.1.2.2
dnscrypt-proxy-android v2.1.2.1
Added
dct-at1
resolver (DNSCrypt | IPv4 only | Non-logging | Non-filtering | DNSSEC | Vienna, Austria).dct-de1
resolver (DNSCrypt | IPv4 only | Non-logging | Non-filtering | DNSSEC | Düsseldorf, Germany).dct-ru1
resolver (DNSCrypt | IPv4 only | Non-logging | Non-filtering | DNSSEC | Moscow, Russia).dnswarden-uncensor-dc-swiss
resolver (Hosted in Switzerland. For more information look here or here).dotya.ml
resolver (Free, uncensored, DNSSEC-validated, non-logging DNSCrypt server hosted in Nuremberg, Germany on Contabo servers. Operated by dotya.ml, configs live here).sby-limotelu
resolver (non-censoring, non-logging, DNSSEC-capable Hosted in Surabaya, Indonesia (Dnscrypt) https://limotelu.org maintained by poentodewo).sgp-dn53
resolver (non-censoring, non-logging, DNSSEC-capable Hosted in Singapore (Dnscrypt) https://limotelu.org maintained by poentodewo).starrydns
resolver (DNSCrypt server in Singapore, no filter, no logs, DNSSEC support).
Changed
- Optimized relays.
- Use dns.watch
resolver1
andresolver2
asbootstrap_resolvers
. - Use dns.watch
resolver1
asnetprobe_address
.
Removed
breddns
resolver (unresponsive).dnswarden-uncensor-fr1-dc
resolver (changed).dnswarden-uncensor-ind1-dc
resolver (changed).dnswarden-uncensor-sg1-dc
resolver (changed).dnswarden-uncensor-us1-dc
resolver (changed).moulticast-fr-ipv4
resolver (unresponsive).moulticast-sg-ipv4
resolver (unresponsive).moulticast-uk-ipv4
resolver (unresponsive).pwoss.org-dnscrypt
resolver (unresponsive).
Full Changelog: 2.1.2...2.1.2.1
dnscrypt-proxy-android v2.1.2
Upstream
- Support for DoH over HTTP/3 (DoH3, HTTP over QUIC) has been added.
Compatible servers will automatically use it. Note that QUIC uses UDP
(usually over port 443, like DNSCrypt) instead of TCP. - In previous versions, memory usage kept growing due to channels not
being properly closed, causing goroutines to pile up. This was fixed,
resulting in an important reduction of memory usage. Thanks to
@lifenjoiner for investigating and fixing this! - DNS64:
CNAME
records are now translated like other responses.
Thanks to @ignoramous for this! - A relay whose name has been configured, but doesn't exist in the
list of available relays is now a hard error. Thanks to @lifenjoiner! - Mutexes/locking: bug fixes and improvements, by @ignoramous
- Official packages now include linux/riscv64 builds.
dnscrypt-proxy -resolve
now reports if ECS (EDNS-clientsubnet) is
supported by the server.dnscrypt-proxy -list
now includes ODoH (Oblivious DoH) servers.- Local DoH: queries made using the
GET
method are now handled. - The service can now be installed on OpenRC-based systems.
PTR
queries are now supported for cloaked domains. Contributed by
Ian Bashford, thanks!
Added
- Scripts in
post-fs-data.sh
file for force disable IPv6 connections at OS level, preventing possible leaks. breddns
resolver (Non-logging DNSCrypt server located in Luxembourg, operated by @tmclo).dnswarden-uncensor-fr1-dc
resolver (Hosted in France. For more information look here or here.).dnswarden-uncensor-ind1-dc
resolver (Hosted in India. For more information look here or here.).dnswarden-uncensor-sg1-dc
resolver (Hosted in Singapore. For more information look here or here.).dnswarden-uncensor-us1-dc
resolver (Hosted in USA (Dallas). For more information look here or here.).
Changed
- Adjusted
versionCode
inmodule.prop
file (more easy share beta and manage minor dnscrypt-proxy versions with two digits). - Optimized relays.
Removed
dnswarden-asia-uncensor-dcv4
resolver (changed).dnswarden-eu-uncensor-dcv4
resolver (changed).dnswarden-us-uncensor-dcv4
resolver (changed).
Full Changelog: 2.1.1-3...2.1.2
dnscrypt-proxy-android v2.1.1-3
Added
plan9dns-fl
resolver (Miami Florida, US No-logs, no-filters, DNSSEC -info https://jlongua.github.io/plan9-dns).plan9dns-mx
resolver (Mexico City, Mexico No-logs, no-filters, DNSSEC -info https://jlongua.github.io/plan9-dns).plan9dns-nj
resolver (Piscataway New Jersey, US No-logs, no-filters, DNSSEC -info https://jlongua.github.io/plan9-dnsPiscataway).techsaviours.org-dnscrypt
resolver (No filter | No logs | DNSSEC | Nuremberg, Germany (netcup) | Maintained by https://techsaviours.org/).
Changed
- Optimized relays.
Fixed
- Changelog display issues in Magisk app.
Removed
bcn-dnscrypt
resolver (ceased).dns.digitalsize.net
resolver (DoH).dct-at1
resolver (temporarily down).dct-de1
resolver (temporarily down).dct-ru1
resolver (temporarily down).gombadi-syd
resolver (ceased).moulticast-ca-ipv4
resolver (unresponsive).moulticast-de-ipv4
resolver (unresponsive).plan9-ns1
resolver (changed).plan9-ns2
resolver (changed).
Full Changelog: 2.1.1-2...2.1.1-3
dnscrypt-proxy-android v2.1.1-2
Fixed
- Random connection issues under mobile data. (see DNSCrypt/dnscrypt-proxy/discussions/2020)
Removed
dct-ru2
resolver (ceased).pf-dnscrypt
resolver (unresponsive).zackptg5-us-il-ipv4
resolver (ceased).
Full Changelog: 2.1.1-1...2.1.1-2