AdGuard Home v0.108.0-b.47

Changes compared to the previous beta, v0.108.0-b.46. See CHANGELOG.md for all changes.

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-39323 and CVE-2023-39325 Go vulnerabilities fixed in Go 1.20.9 and Go 1.20.10.

Added

• Ability to edit static leases on DHCP settings page (#1700).

• Ability to specify for how long clients should cache a filtered response, using the Blocked response TTL field on the DNS settings page (#4569).

Changed

• ipset entries are updated more often (#6233).

• Node.JS 16 is now required to build the frontend.

Fixed

• Incorrect domain-specific upstream matching for DS queries (#6156).

• Improper validation of password length (#6280).

• Wrong algorithm for filtering self addresses from the list of private upstream DNS servers (#6231).

• An accidental change in DNS rewrite priority (#6226).

AdGuard Home v0.107.39

The spooky season may soon be upon us :jack_o_lantern:, but we're not afraid to ship a new release with some new features and a few bug fixes!

Full changelog

See also the v0.107.39 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-39323 and CVE-2023-39325 Go vulnerabilities fixed in Go 1.20.9 and Go 1.20.10.

Added

• Ability to edit static leases on DHCP settings page (#1700).

• Ability to specify for how long clients should cache a filtered response, using the Blocked response TTL field on the DNS settings page (#4569).

Changed

• ipset entries are updated more often (#6233).

• Node.JS 16 is now required to build the frontend.

Fixed

• Incorrect domain-specific upstream matching for DS queries (#6156).

• Improper validation of password length (#6280).

• Wrong algorithm for filtering self addresses from the list of private upstream DNS servers (#6231).

• An accidental change in DNS rewrite priority (#6226).

AdGuard Home v0.108.0-b.46

Changes compared to the previous beta, v0.108.0-b.45. See CHANGELOG.md for all changes.

Full changelog

Fixed

• Incorrect original answer when a response is filtered (#6183).

• Comments in the Fallback DNS servers field in the UI (#6182).

• Empty or default Safe Browsing and Parental Control settings (#6181).

• Various UI issues.

AdGuard Home v0.107.38

Releases are like fruit: the tastier the apple, the more likely there's a bug in it somewhere. It turns out that our previous release was quite delicious! This hotfix is meant to deal with all the remaining bugs.

Full changelog

See also the v0.107.38 GitHub milestone.

Fixed

• Incorrect original answer when a response is filtered (#6183).

• Comments in the Fallback DNS servers field in the UI (#6182).

• Empty or default Safe Browsing and Parental Control settings (#6181).

• Various UI issues.

AdGuard Home v0.108.0-b.45

Changes compared to the previous beta, v0.108.0-b.44. See CHANGELOG.md for all changes.

Acknowledgements

A special thanks to our open-source contributor, @ssrahul96, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-39318, CVE-2023-39319, and CVE-2023-39320 Go vulnerabilities fixed in Go 1.20.8.

Added

• AdBlock-style syntax support for ignored domains in logs and statistics (#5720).

• Strict-Transport-Security header in the HTTP API and DNS-over-HTTPS responses when HTTPS is forced (#2998). See RFC 6797.

• UI for the schedule of the service-blocking pause (#951).

Changed

Configuration Changes

In this release, the schema version has changed from 25 to 27.

• Ignore rules blocking . in querylog.ignored and statistics.ignored have been migrated to AdBlock syntax (|.^). To rollback this change, restore the rules and change the schema_version back to 26.

• Filtering-related settings have been moved from dns section of the YAML configuration file to the new section filtering:

  # BEFORE:
  'dns':
      'filtering_enabled': true
      'filters_update_interval': 24
      'parental_enabled': false
      'safebrowsing_enabled': false
      'safebrowsing_cache_size': 1048576
      'safesearch_cache_size': 1048576
      'parental_cache_size': 1048576
      'safe_search':
          'enabled': false
          'bing': true
          'duckduckgo': true
          'google': true
          'pixabay': true
          'yandex': true
          'youtube': true
      'rewrites': []
      'blocked_services':
          'schedule':
              'time_zone': 'Local'
          'ids': []
      'protection_enabled':        true,
      'blocking_mode':             'custom_ip',
      'blocking_ipv4':             '1.2.3.4',
      'blocking_ipv6':             '1:2:3::4',
      'blocked_response_ttl':      10,
      'protection_disabled_until': 'null',
      'parental_block_host':       'p.dns.adguard.com',
      'safebrowsing_block_host':   's.dns.adguard.com'
  
  # AFTER:
  'filtering':
      'filtering_enabled': true
      'filters_update_interval': 24
      'parental_enabled': false
      'safebrowsing_enabled': false
      'safebrowsing_cache_size': 1048576
      'safesearch_cache_size': 1048576
      'parental_cache_size': 1048576
      'safe_search':
          'enabled': false
          'bing': true
          'duckduckgo': true
          'google': true
          'pixabay': true
          'yandex': true
          'youtube': true
      'rewrites': []
      'blocked_services':
          'schedule':
              'time_zone': 'Local'
          'ids': []
      'protection_enabled':        true,
      'blocking_mode':             'custom_ip',
      'blocking_ipv4':             '1.2.3.4',
      'blocking_ipv6':             '1:2:3::4',
      'blocked_response_ttl':      10,
      'protection_disabled_until': 'null',
      'parental_block_host':       'p.dns.adguard.com',
      'safebrowsing_block_host':   's.dns.adguard.com',

  To rollback this change, remove the new object filtering, set back filtering properties in dns section, and change the schema_version back to 25.

Fixed

• Incorrect display date on statistics graph (#5793).

• Missing query log entries and statistics on service restart (#6100).

AdGuard Home v0.107.37

The summer has come and gone, leaving behind a decent harvest of long-awaited features and improvements, with a side order of bug fixes :grapes:!

Service blocking pause schedule

Users can now easily set pauses for the service blocking filter. For example, you can block social networks throughout the day, but allow yourself 30 minutes after work.

While this feature has been in internal development for several months, in this release we are glad to finally present it in the web UI.

Fallback servers

Another long-awaited feature is the fallback servers, which are used when the main upstream DNS servers cannot be reached.

The syntax there is the same as for the main upstream input, so you can set different fallback servers for different domains.

Upstream statistics

Another feature related to DNS upstreams is the new upstream statistics shown on the dashboard.

These allow users to see which upstreams are faster than others, as well as which upstreams are being used the most.

Acknowledgements

A special thanks to our open-source contributor, @ssrahul96, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!

Full changelog

See also the v0.107.37 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-39318, CVE-2023-39319, and CVE-2023-39320 Go vulnerabilities fixed in Go 1.20.8.

Added

• AdBlock-style syntax support for ignored domains in logs and statistics (#5720).

• Strict-Transport-Security header in the HTTP API and DNS-over-HTTPS responses when HTTPS is forced (#2998). See RFC 6797.

• UI for the schedule of the service-blocking pause (#951).

• IPv6 hints are now filtered in case IPv6 addresses resolving is disabled (#6122).

• The ability to set fallback DNS servers in the configuration file and the UI (#3701).

• While adding or updating blocklists, the title can now be parsed from ! Title: definition of the blocklist's source (#6020).

• The ability to filter DNS HTTPS records including IPv4 and IPv6 hints (#6053).

• Two new metrics showing total number of responses from each upstream DNS server and their average processing time in the Web UI (#1453).

• The ability to set the port for the pprof debug API, see configuration changes below.

Changed

• $dnsrewrite rules containing IPv4-mapped IPv6 addresses are now working consistently with legacy DNS rewrites and match the AAAA requests.

• For non-A and non-AAAA requests, which has been filtered, the NODATA response is returned if the blocking mode isn't set to Null IP. In previous versions it returned NXDOMAIN response in such cases.

Configuration Changes

In this release, the schema version has changed from 24 to 27.

• Ignore rules blocking . in querylog.ignored and statistics.ignored have been migrated to AdBlock syntax (|.^). To rollback this change, restore the rules and change the schema_version back to 26.

• Filtering-related settings have been moved from dns section of the YAML configuration file to the new section filtering:

  # BEFORE:
  'dns':
      'filtering_enabled': true
      'filters_update_interval': 24
      'parental_enabled': false
      'safebrowsing_enabled': false
      'safebrowsing_cache_size': 1048576
      'safesearch_cache_size': 1048576
      'parental_cache_size': 1048576
      'safe_search':
          'enabled': false
          'bing': true
          'duckduckgo': true
          'google': true
          'pixabay': true
          'yandex': true
          'youtube': true
      'rewrites': []
      'blocked_services':
          'schedule':
              'time_zone': 'Local'
          'ids': []
      'protection_enabled':        true,
      'blocking_mode':             'custom_ip',
      'blocking_ipv4':             '1.2.3.4',
      'blocking_ipv6':             '1:2:3::4',
      'blocked_response_ttl':      10,
      'protection_disabled_until': 'null',
      'parental_block_host':       'p.dns.adguard.com',
      'safebrowsing_block_host':   's.dns.adguard.com'
  
  # AFTER:
  'filtering':
      'filtering_enabled': true
      'filters_update_interval': 24
      'parental_enabled': false
      'safebrowsing_enabled': false
      'safebrowsing_cache_size': 1048576
      'safesearch_cache_size': 1048576
      'parental_cache_size': 1048576
      'safe_search':
          'enabled': false
          'bing': true
          'duckduckgo': true
          'google': true
          'pixabay': true
          'yandex': true
          'youtube': true
      'rewrites': []
      'blocked_services':
          'schedule':
              'time_zone': 'Local'
          'ids': []
      'protection_enabled':        true,
      'blocking_mode':             'custom_ip',
      'blocking_ipv4':             '1.2.3.4',
      'blocking_ipv6':             '1:2:3::4',
      'blocked_response_ttl':      10,
      'protection_disabled_until': 'null',
      'parental_block_host':       'p.dns.adguard.com',
      'safebrowsing_block_host':   's.dns.adguard.com',

  To rollback this change, remove the new object filtering, set back filtering properties in dns section, and change the schema_version back to 25.

• Property debug_pprof which used to setup profiling HTTP handler, is now moved to the new pprof object under http section. The new object contains properties enabled and port:

  # BEFORE:
  'debug_pprof': true
  
  # AFTER:
  'http':
      'pprof':
          'enabled': true
          'port': 6060

  Note that the new default 6060 is used as default. To rollback this change, remove the new object pprof, set back debug_pprof, and change the schema_version back to 24.

Fixed

• Incorrect display date on statistics graph (#5793).

• Missing query log entries and statistics on service restart (#6100).

• Occasional DNS-over-QUIC and DNS-over-HTTP/3 errors (#6133).

• Legacy DNS rewrites containing IPv4-mapped IPv6 addresses are now matching the AAAA requests, not A (#6050).

• File log configuration, such as max_size, being ignored (#6093).

• Panic on using a single-slash filtering rule.

• Panic on shutting down while DNS requests are in process of filtering (#5948).

AdGuard Home v0.108.0-b.44

Changes compared to the previous beta, v0.108.0-b.43. See CHANGELOG.md for all changes.

Full changelog

Added

• IPv6 hints are now filtered in case IPv6 addresses resolving is disabled (#6122).

• The ability to set fallback DNS servers in the configuration file (#3701).

• While adding or updating blocklists, the title can now be parsed from ! Title: definition of the blocklist's source (#6020).

• The ability to filter DNS HTTPS records including IPv4/v6 hints (#6053).

• Two new metrics showing total number of responses from each upstream DNS server and their average processing time in the Web UI (#1453).

Changed

• $dnsrewrite rules containing IPv4-mapped IPv6 addresses are now working consistently with legacy DNS rewrites and match the AAAA requests.

• For non-A and non-AAAA requests, which has been filtered, the NODATA response is returned if the blocking mode isn't set to Null IP. In previous versions it returned NXDOMAIN response in such cases.

Fixed

• Occasional DNS-over-QUIC and DNS-over-HTTP/3 errors (#6133).

• Legacy DNS rewrites containing IPv4-mapped IPv6 addresses are now matching the AAAA requests, not A (#6050).

• File log configuration, such as max_size, being ignored (#6093).

• Panic on using a single-slash filtering rule.

• Panic on shutting down while DNS requests are in process of filtering (#5948).

AdGuard Home v0.108.0-b.43

Changes compared to the previous beta, v0.108.0-b.42. See CHANGELOG.md for all changes.

Full changelog

Security

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

Changed

• Improved reliability filtering-rule list updates on Unix systems.

Configuration Changes

In this release, the schema version has changed from 24 to 25.

• Property debug_pprof which used to setup profiling HTTP handler, is now moved to the new pprof object under http section. The new object contains properties enabled and port:

  # BEFORE:
  'debug_pprof': true
  
  # AFTER:
  'http':
      'pprof':
          'enabled': true
          'port': 6060

  Note that the new default 6060 is used as default. To rollback this change, remove the new object pprof, set back debug_pprof, and change the schema_version back to 24.

Deprecated

• Go 1.20 support. Future versions will require at least Go 1.21 to build.

Fixed

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

AdGuard Home v0.107.36

A small bugfix and security release. We are working on new features in future releases.

Full changelog

See also the v0.107.36 GitHub milestone.

Security

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

Deprecated

• Go 1.20 support. Future versions will require at least Go 1.21 to build.

Fixed

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

AdGuard Home v0.107.35

In the previous release, we optimized the filtering-rule list updates, achieving up to three times speedup in some cases. However, the new algorithm proved to be too strict, so in this release we have relaxed its validations while maintaining the optimization for more typical filtering-rule lists :racing_car:.

As always, there are other minor bug fixes in this release as well.

Full changelog

See also the v0.107.35 GitHub milestone.

Changed

• Improved reliability filtering-rule list updates on Unix systems.

Fixed

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

Removed

• Default exposure of the non-standard ports 784 and 8853 for DNS-over-QUIC in the Dockerfile.