Download AdGuard Home 0.107.26

AdGuard Home version 0.107.26 has been released. With this software, a DNS server can be set up at home to block advertisements and malware on the entire network. It is therefore comparable to Pi-hole. AdGuard Home works on a machine with 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 following changes and improvements have been made in this release:

AdGuard Home v0.107.26

Today’s one features further customization options for outbound queries, new option to drop requests based on their question types, and various bug fixes.

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-24532 Go vulnerability fixed in Go 1.19.7.

Added

• 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.
• The ability to use dnstype rules in the disallowed domains list (#5468). This allows dropping requests based on their question types.

Configuration Changes

In this release, the schema version has changed from 16 to 17.

• Property edns_client_subnet, which in schema versions 16 and earlier used to be a part of the dns object, is now part of the dns.edns_client_subnet object: # BEFORE: ‘dns’: # … ‘edns_client_subnet’: false # AFTER: ‘dns’ : # … ‘edns_client_subnet’: ‘enabled’: false ‘use_custom’: false ‘custom_ip’: ”

  To rollback this change, move the value of dns.edns_client_subnet.enabled into the dns.edns_client_subnet, remove the fields dns.edns_client_subnet.enabled, dns.edns_client_subnet.use_custom, dns.edns_client_subnet.custom_ip, and change the schema_version back to 16.

Fixed

• Obsolete value of the Interface MTU DHCP option is now omitted (#5281).
• Various dark theme bugs (#5439, #5441, #5442, #5515).
• Automatic update on MIPS64 and little-endian 32-bit MIPS architectures (#5270, #5373).
• Requirements to domain names in domain-specific upstream configurations have been relaxed to meet those from RFC 3696 (#4884).