AdguardTeam/AdGuardHome v0.107.26

AdGuard Home v0.107.26

on GitHub

We swear, winters only get longer over the years; however, yet another one is behind us, and what a better way to celebrate Spring 💐 than to release an AdGuard Home update. Today’s one features further customization options for outbound queries, new option to drop requests based on their question types, and various bugfixes.

Full changelog

See also the v0.107.26 GitHub milestone.

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.

Changed

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).