Release Notes: This release ships with the Sodium library, which brings significant performance improvements over previous versions. A new command-line switch, --loglevel, has been added to adjust the log verbosity.
Release Notes: This is a major release with numerous bugfixes, compatibility improvements, and new features. dnscrypt-proxy can now be extended using dynamically loaded plugins that can inspect and alter DNS packets. Upgrading is recommended, especially on Windows and Android.
Release Notes: The Android build script has been fixed, memory leaks when fetching certificates have been fixed, a bad use-after-free condition has been fixed, and uninitialized variables have been initialized. Updating is highly recommended, especially on Windows. The plugin API has been documented, and a new configuration flag, --enable-relaxed-plugins-permissions, allows loading plugin files which are not owned by root or by the current user.
Release Notes: dnscrypt-proxy can now use plugins to alter/inspect queries and responses before and after they are relayed. The default max payload size has been trimmed to 1,252 bytes for compatibility with some scary network setups. The --local-port and --resolver-port options are gone for good. They had been deprecated for a while.
Release Notes: dnscrypt-proxy and hostip can now be compiled for Android and Solaris. The proxy can now run as a Windows service, with startup options read from the Windows registry.
Release Notes: dnscrypt-proxy is no longer in beta.
Release Notes: This release fixes a regression on Linux. The proxy now resends datagrams after running out of memory or after the send queue was full.
Release Notes: A new tool, hostip, can resolve host names before dnscrypt-proxy is started. This should help with resolving chicken-and-egg problems on routers. The --local-port and --resolver-port options have been deprecated. Stability has been improved on Windows.
Release Notes: This release is a major rewrite based on libevent, featuring smaller binaries, lower latency, and a significant reduction of memory usage. The maximum number of simultaneous queries is now global, not per-protocol. The default resolver port has been changed to 443. Additional dtrace probes have been added.
Release Notes: The --tcp-port switch is gone. Alternative ports for the upstream resolver can now be specified with --resolver-port, and a new switch, --tcp-only, forces usage of TCP.