AdGuard Home - Package Updates
Pinned
AdGuard Home
-
[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.
-
[1.7.3]
- Update AdGuard Home to 0.108.0-b.31
- Full changelog
- The new HTTP API POST /control/protection, that updates protection state and adds an optional pause duration (#1333). The format of request body is described in openapi/openapi.yaml. The duration of this pause could also be set with the config field protection_disabled_until in dns section of the YAML configuration file.
- The ability to create a static DHCP lease from a dynamic one more easily (#3459).
- Two new HTTP APIs, PUT /control/stats/config/update and GET control/stats/config, which can be used to set and receive the query log configuration. See openapi/openapi.yaml for the full description.
- Two new HTTP APIs, PUT /control/querylog/config/update and GET control/querylog/config, which can be used to set and receive the statistics configuration. See openapi/openapi.yaml for the full description.
- The ability to set custom IP for EDNS Client Subnet by using the DNS-server configuration section on the DNS settings page in the UI (#1472).
- The ability to manage safesearch for each service by using the new safe_search field (#1163).
- ARPA domain names containing a subnet within private networks now also considered private, behaving closer to RFC 6761 (#5567).
-
[1.7.4]
- Update AdGuard Home to 0.108.0-b.32
- Full changelog
- Go version has been updated to prevent the possibility of exploiting the CVE-2023-24534, CVE-2023-24536, CVE-2023-24537, and CVE-2023-24538 Go vulnerabilities fixed in Go 1.19.8.
- The ability to make bootstrap DNS lookups prefer IPv6 addresses to IPv4 ones using the new dns.bootstrap_prefer_ipv6 configuration file property (#4262).
-
[1.7.5]
- Update AdGuard Home to 0.108.0-b.33
- Full changelog
- The ability to exclude client activity from the query log or statistics by using the new properties ignore_querylog and ignore_statistics of the items of the clients.persistent array (#1717, #4299). The UI changes are coming in the upcoming releases.
- Better profiling information when debug_pprof is set to true.
- IPv6 support in Safe Search for some services.
-
[1.7.6]
- Update AdGuard Home to 0.108.0-b.34
- Full changelog
- The ability to exclude client activity from the query log or statistics by editing client's settings on the respective page in the UI (#1717, #4299).
- Stored DHCP leases moved from leases.db to data/leases.json. The file format has also been optimized.
- Provided bootstrap servers are now used to resolve the hostnames of plain UDP/TCP upstream servers.
- The github.com/mdlayher/raw dependency has been temporarily returned to support raw connections on Darwin (#5712).
- Incorrect recording of blocked results as “Blocked by CNAME or IP” in the query log (#5725).
- All Safe Search services are unchecked by default.
-
[1.7.7]
- Update AdGuard Home to 0.108.0-b.35
- Full changelog
- Go version has been updated to prevent the possibility of exploiting the CVE-2023-29402, CVE-2023-29403, and CVE-2023-29404 Go vulnerabilities fixed in Go 1.19.10.
- The ability to edit rewrite rules via PUT /control/rewrite/update HTTP API (#1577).
- Unquoted IPv6 bind hosts with trailing colons erroneously considered unspecified addresses are now properly validated (#5752).
- Incorrect Content-Type header value in POST /control/version.json and GET /control/dhcp/interfaces HTTP APIs (#5716).
-
[1.7.12]
- Update AdGuard Home to 0.108.0-b.40
- Full changelog
- Improved CPU and RAM consumption during updates of filtering-rule lists.
- Two unspecified IPs when a host is blocked in two filter lists (#5972).
- Incorrect setting of Parental Control cache size.
- Excessive RAM and CPU consumption by Safe Browsing and Parental Control filters (#5896).
-
[1.7.13]
- Update AdGuard Home to 0.108.0-b.41
- Full changelog
- Go version has been updated to prevent the possibility of exploiting the CVE-2023-29406 Go vulnerability fixed in Go 1.19.11.
- Ability to ignore queries for the root domain, such as NS . queries (#5990).
-
[1.7.14]
- Update AdGuard Home to 0.108.0-b.42
- Full changelog
- Occasional client information lookup failures that could lead to the DNS server getting stuck (#6006).
- bufio.Scanner: token too long and other errors when trying to add filtering-rule lists with lines over 1024 bytes long or containing cosmetic rules (#6003).
-
[1.7.15]
- Update AdGuard Home to 0.108.0-b.43
- Full changelog
- Go version has been updated to prevent the possibility of exploiting the CVE-2023-29409 Go vulnerability fixed in [Go 1.20.7][go-1.20.7].
- Improved reliability filtering-rule list updates on Unix systems.
- In this release, the schema version has changed from 24 to 25.
- Inability to block queries for the root domain, such as NS . queries, using the Disallowed domains feature on the DNS settings page (#6049). Users who want to block . queries should use the |.^ AdBlock rule or a similar regular expression.
- Client hostnames not resolving when upstream server responds with zero-TTL records (#6046).
