Download AdGuard Home 0.107.17

AdGuard Home version 0.107.17 has been released. With this software, a DNS server can be set up at home to block advertisements and malware on the entire network, among other things. It is therefore comparable to Pi-hole. AdGuard Home works on a machine running Windows, macOS, Linux or FreeBSD, is also able to protect against phishing and has parental control. The program can be discussed on our own forum. The changelog for this release can be found below:

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2022-41716 Go vulnerability fixed in Go 1.18.8.

Added

• The warning message when adding a certificate having no IP addresses (#4898).
• Several new blockable services (#3972). Those will now be more in sync with the services that are already blockable in AdGuard DNS.
• A new HTTP API, GET /control/blocked_services/all, that lists all available blocked services and their data, such as SVG icons (#3972).
• The new optional tls.override_tls_ciphers property, which allows overriding TLS ciphers used by AdGuard Home (#4925, #4990).
• The ability to serve DNS on link-local IPv6 addresses (#2926).
• The ability to put Client IDs into DNS-over-HTTPS hostnames as opposed to URL paths (#3418). Note that AdGuard Home checks the server name only if the URL does not contain a ClientID.

changed

• DNS-over-TLS resolvers aren’t returned anymore when the configured TLS certificate contains no IP addresses (#4927).
• Responses with SERVFAIL code are now cached for at least 30 seconds.

Deprecated

• The GET /control/blocked_services/services HTTP API; use the new GET /control/blocked_services/all API instead (#3972).

Fixed

• ClientIDs not working when using DNS-over-HTTPS with HTTP/3.
• Editing the URL of an enabled rule list also includes validation of the filter contents preventing from saving a bad one (#4916).
• The default value of dns.cache_size accidentally set to 0 has now been reverted to 4 MiB (#5010).
• Responses for which the DNSSEC validation had explicitly been omitted aren’t cached now (#4942).
• WebUI not switching to HTTP/3 (#4986, #4993).