AdGuard Home - Package Updates
-
[1.4.10]
- Update AdGuard Home to 0.107.10
- Full changelog
- Arabic localization.
- Support for Discovery of Designated Resolvers (DDR) according to the RFC draft (#4463).
- DHCP not working on most OSs (#4836).
- invalid argument errors during update checks on older Linux kernels (#4670).
- Data races and concurrent map access in statistics module (#4358, #4342).
-
[1.5.0]
- Update AdGuard Home to 0.108.0
- Full changelog
- New bool, dur, u8, and u16 DHCP options to provide more convenience on options control by setting values in a human-readable format (#4705). See also a Wiki page.
- New del DHCP option which removes the corresponding option from server's response (#4337). See also a Wiki page.
- A new HTTP API, GET /control/blocked_services/services, that lists all available blocked services (#4535).
- The DHCP options handling is now closer to the RFC 2131 (#4705).
- When the DHCP server is enabled, queries for domain names under dhcp.local_domain_name not pointing to real DHCP client hostnames are now processed by filters (#4865).
- The DHCPREQUEST handling is now closer to the RFC 2131 (#4863).
- The internal DNS client, used to resolve hostnames of external clients and also during automatic updates, now respects the upstream mode settings for the main DNS client (#4403).
-
[1.5.2]
- Update AdGuard Home to 0.108.0-b.17
- Full changelog
- Security: As an additional CSRF protection measure, AdGuard Home now ensures that requests that change its state but have no body (such as POST /control/stats_reset requests) do not have a Content-Type header set on them
-
[1.5.3]
- Update AdGuard Home to 0.108.0-b.18
- Full changelog
- Go version has been updated to prevent the possibility of exploiting the CVE-2022-2879, CVE-2022-2880, and CVE-2022-41715 Go vulnerabilities fixed in Go 1.18.7.
- The ability to put ClientIDs 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.
-
[1.5.4]
- Update AdGuard Home to 0.108.0-b.19
- Full changelog
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).
-
[1.5.5]
- Update AdGuard Home to 0.108.0-b.20
- Full changelog
- 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 ability to put ClientIDs 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.
-
[1.5.9]
- Update AdGuard Home to 0.108.0-b.24
- Full changelog
- The URLs of the default filters for new installations are synchronized to those introduced in v0.107.20 (#5238).
- Errors popping up during updates of settings, which could sometimes cause the server to stop responding (#5251).
-
[1.5.11]
- Update AdGuard Home to 0.108.0-b.26
- Full changelog
Added - DNS64 support (#5117). The function may be enabled with new use_dns64 field under dns object in the configuration along with dns64_prefixes, the set of exclusion prefixes to filter AAAA responses. The Well-Known Prefix (64:ff9b::/96) is used if no custom prefixes are specified.
- Filtering rules with * as the hostname not working properly (#5245).
- Various dark theme bugs (#5375).
-
[1.7.1]
- Update AdGuard Home to 0.108.0-b.29
- Full changelog
- The ability to use dnstype rules in the disallowed domains list (#5468). This allows dropping requests based on their question types.
- Various dark theme bugs (#5439, #5441, #5442, #5515).
- Automatic update on MIPS64 and little-endian 32-bit MIPS architectures (#5270, #5373).
-
[1.7.2]
- Update AdGuard Home to 0.108.0-b.30
- Full changelog
- The ability to set custom IP for EDNS Client Subnet by using the new dns.edns_client_subnet.use_custom and dns.edns_client_subnet.custom_ip fields (#1472). The UI changes are coming in the upcoming releases.
- In this release, the schema version has changed from 16 to 17. Check the full changelog for details.
