AdGuard Home v0.107.44

They say, when you do your job well, nobody ever notices it. We'd like to believe this is the case, as today's update won't knock your socks off with any new major features or anything of the sort. Instead, we “oil the gears” with spot changes and assorted bugfixes 🔧.

Acknowledgements

A special thanks to our open-source contributors: @bakito, and @satheshshiva, 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.44 GitHub milestone.

Added

• Timezones in the Etc/ area to the timezone list (#6568).

• The schema version of the configuration file to the output of running AdGuardHome (or AdGuardHome.exe) with -v --version command-line options (#6545).

• Ability to disable plain-DNS serving via UI if an encrypted protocol is already used (#1660).

Changed

• The bootstrapped upstream addresses are now updated according to the TTL of the bootstrap DNS response (#6321).

• Logging level of timeout errors is now error instead of debug (#6574).

• The field "upstream_mode" in POST /control/dns_config and GET /control/dns_info HTTP APIs now accepts load_balance value. Check openapi/CHANGELOG.md for more details.

Configuration changes

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

• The new property clients.persistent.*.uid, which is a unique identifier of the persistent client.

• The properties dns.all_servers and dns.fastest_addr were removed, their values migrated to newly added field dns.upstream_mode that describes the logic through which upstreams will be used. See also a Wiki page.

  # BEFORE:
  'dns':
      # …
      'all_servers': true
      'fastest_addr': true
  
  # AFTER:
  'dns':
      # …
      'upstream_mode': 'parallel'

  To rollback this change, remove the new field upstream_mode, set back dns.all_servers and dns.fastest_addr properties in dns section, and change the schema_version back to 27.

Fixed

• “Invalid AddrPort” in the Private reverse DNS servers section on the Settings → DNS settings page.
• Panic on using --no-etc-hosts flag (#6644).
• Schedule display in the client settings after creating or updating.
• Zero value in querylog.size_memory disables logging (#6570).
• Non-anonymized IP addresses on the dashboard (#6584).
• Maximum cache TTL requirement when editing minimum cache TTL in the Web UI (#6409).
• Load balancing algorithm stuck on a single server (#6480).
• Statistics for 7 days displayed as 168 hours on the dashboard.
• Pre-filling the Edit static lease window with data (#6534).
• Names defined in the /etc/hosts for a single address family wrongly considered undefined for another family (#6541).
• Omitted CNAME records in safe search results, which can cause YouTube to not work on iOS (#6352).

AdGuard Home v0.108.0-b.52

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

Full changelog

Added

• Etc timezones to the timezone list (#6568).
• The schema version of the configuration file to the output of running AdGuardHome (or AdGuardHome.exe) with -v --version command-line options (#6545).
• Ability to disable plain-DNS serving via UI if an encrypted protocol is already used (#1660).

Changed

• The bootstrapped upstream addresses now updated according to the TTL of the bootstrap DNS response (#6321).
• Logging level of timeout errors is now error instead of debug (#6574).
• The field "upstream_mode" in POST /control/dns_config and GET /control/dns_info HTTP APIs now accepts load_balance value. Check openapi/CHANGELOG.md for more details.

Configuration changes

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

• The new property clients.persistent.*.uid, which is unique identifier of the persistent client.
• The properties dns.all_servers and dns.fastest_addr were removed, their values migrated to newly added field dns.upstream_mode that describes the logic through which upstreams will be used. See also a Wiki page.

# BEFORE:
'dns':
    # …
    'all_servers': true
    'fastest_addr': true

# AFTER:
'dns':
    # …
    'upstream_mode': 'parallel'

To rollback this change, remove the new field upstream_mode, set back dns.all_servers and dns.fastest_addr properties in dns section, and change the schema_version back to 27.

Fixed

• Panic on using --no-etc-hosts flag (#6644).
• Schedule display in the client settings after creating or updating.
• Zero value in querylog.size_memory disables logging (#6570).
• Non-anonymized IP addresses on the dashboard (#6584).
• Maximum cache TTL requirement when editing minimum cache TTL in the Web UI (#6409).
• Load balancing algorithm stuck on a single server (#6480).
• Statistics for 7 days displayed as 168 hours on the dashboard.
• Pre-filling the Edit static lease window with data (#6534).
• Names defined in the /etc/hosts for a single address family wrongly considered undefined for another family (#6541).
• Omitted CNAME records in safe search results, which can cause YouTube to not work on iOS (#6352).
• Incorrect handling of IPv4-in-IPv6 addresses when binding to an unspecified address on some machines (#6510).

AdGuard Home v0.107.43

Everybody needs something to keep themselves warm during the cold winter days ❄️. Many people opt for hot coffee ☕ or hot chocolate, but we at AdGuard prefer hotfixes 🔥.

Full changelog

See also the v0.107.43 GitHub milestone.

Fixed

• Incorrect handling of IPv4-in-IPv6 addresses when binding to an unspecified address on some machines (#6510).

AdGuard Home v0.108.0-b.51

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

Full changelog

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-39326, CVE-2023-45283, and CVE-2023-45285 Go vulnerabilities fixed in Go 1.20.12.

Added

• Ability to set client's custom DNS cache (#6263).

Fixed

• Memory leak when using parallel queries (#6438).

AdGuard Home v0.107.42

As the winter holidays approach, many of us begin to think about what gifts we will give and receive 🎁. With AdGuard, the holidays come early: we decided not to wait too long and present you with this new version of AdGuard Home today!

Among the long-awaited features in this release are the option to enable caching for persistent clients with custom DNS upstream configuration and the option to disable plain DNS for better security.

Acknowledgements

A special thanks to our open-source contributor, @jefferyto, 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.42 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-39326, CVE-2023-45283, and CVE-2023-45285 Go vulnerabilities fixed in Go 1.20.12.

Added

• Ability to set client's custom DNS cache (#6263).

• Ability to disable plain-DNS serving through configuration file if an encrypted protocol is already enabled (#1660).

• Ability to specify rate limiting settings in the Web UI (#6369).

Changed

Configuration changes

• The new property dns.serve_plain_dns has been added to the configuration file (#1660).

• The property dns.bogus_nxdomain is now validated more strictly.

• Added new properties clients.persistent.*.upstreams_cache_enabled and clients.persistent.*.upstreams_cache_size that describe cache configuration for each client's custom upstream configuration.

Fixed

• ipset entries family validation (#6420).

• Pre-filling the New static lease window with data (#6402).

• Protection pause timer synchronization (#5759).

AdGuard Home v0.108.0-b.50

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

Acknowledgements

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

Full changelog

Added

• Ability to disable plain-DNS serving through configuration file if an encrypted protocol is already used (#1660).

• Ability to specify rate limiting settings in the Web UI (#6369).

Changed

Configuration changes

• The new property dns.serve_plain_dns has been added to the configuration file (#1660).

• The property dns.bogus_nxdomain is now validated more strictly.

• Added new properties clients.persistent.*.upstreams_cache_enabled and clients.persistent.*.upstreams_cache_size that describe cache configuration for each client's custom upstream configuration.

Fixed

• ipset entries family validation (#6420).

• Pre-filling the New static lease window with data (#6402).

• Protection pause timer synchronization (#5759).

AdGuard Home v0.108.0-b.49

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

Acknowledgements

A special thanks to our open-source contributor, @TimTheBig, 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.41 GitHub milestone][ms-v0.107.41].

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-45283 and CVE-2023-45284 Go vulnerabilities fixed in Go 1.20.11.

Added

• Ability to specify subnet lengths for IPv4 and IPv6 addresses, used for rate limiting requests, in the configuration file (#6368).

• Ability to specify multiple domain specific upstreams per line, e.g. [/domain1/../domain2/]upstream1 upstream2 .. upstreamN (#4977).

Changed

• Increased the height of the ready-to-use filter lists dialog (#6358).

• Improved logging of authentication failures (#6357).

Configuration changes

• New properties dns.ratelimit_subnet_len_ipv4 and dns.ratelimit_subnet_len_ipv6 have been added to the configuration file (#6368).

Fixed

• Schedule timezone not being sent (#6401).

• Average request processing time calculation (#6220).

• Redundant truncation of long client names in the Top Clients table (#6338).

• Scrolling column headers in the tables (#6337).

• $important,dnsrewrite rules not overriding allowlist rules (#6204).

• Dark mode DNS rewrite background (#6329).

• Issues with QUIC and HTTP/3 upstreams on Linux (#6335).

AdGuard Home v0.107.41

Bugs are as certain as the change of the seasons 📆. However, in this release we have not only fixed quite a few of them, but also added some features that will make it easier to configure AdGuard Home and protect it from DDoS attacks!

Acknowledgements

A special thanks to our open-source contributor, @TimTheBig, 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.41 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the CVE-2023-45283 and CVE-2023-45284 Go vulnerabilities fixed in Go 1.20.11.

Added

• Ability to specify subnet lengths for IPv4 and IPv6 addresses, used for rate limiting requests, in the configuration file (#6368).

• Ability to specify multiple domain specific upstreams per line, e.g. [/domain1/../domain2/]upstream1 upstream2 .. upstreamN (#4977).

Changed

• Increased the height of the ready-to-use filter lists dialog (#6358).

• Improved logging of authentication failures (#6357).

Configuration changes

• New properties dns.ratelimit_subnet_len_ipv4 and dns.ratelimit_subnet_len_ipv6 have been added to the configuration file (#6368).

Fixed

• Schedule timezone not being sent (#6401).

• Average request processing time calculation (#6220).

• Redundant truncation of long client names in the Top Clients table (#6338).

• Scrolling column headers in the tables (#6337).

• $important,dnsrewrite rules not overriding allowlist rules (#6204).

• Dark mode DNS rewrite background (#6329).

• Issues with QUIC and HTTP/3 upstreams on Linux (#6335).

AdGuard Home v0.107.40

What could be spookier than bugs preventing people from using their networks 👻? Luckily, we're here to bust them with this hotfix release!

Full changelog

See also the v0.107.40 GitHub milestone.

Changed

• Block and Unblock buttons of the query log moved to the tooltip menu (#684).

Fixed

• Dashboard tables scroll issue (#6180).

• The time shown in the statistics is one hour less than the current time (#6296).

• Issues with QUIC and HTTP/3 upstreams on FreeBSD (#6301).

• Panic on clearing query log (#6304).

AdGuard Home v0.108.0-b.48

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

Full changelog

Changed

• "Block" and "Unblock" buttons of the query log moved to the tooltip menu (#684).

Fixed

• Dashboard tables scroll issue (#6180).
• Issues with QUIC and HTTP/3 upstreams on FreeBSD (#6301).
• Panic on clearing query log (#6304).
• The time shown in the statistics is one hour less than the current time (#6296).