AdGuard Home: baixar versions anteriors

It’s not always the big issues: sometimes what you need is a few fixes and tweaks to pump up the overall stability 🔩
Full changelog
See also the v0.107.79 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.6.
- AdGuard Home is now more resistant to resource exhaustion attacks when using DNS-over-QUIC.
This is GHSA-w6v6-f44j-3rj2. We thank @ATinyShoe for reporting this security issue.
Added
- Bootstrap servers configuration now supports comments.
- New property "language" in POST /control/install/check_config and POST /control/install/configure HTTP APIs.
- The user is able to remove the static lease's hostname via the HTTP API.
Changed
- The edge channel has been switched to the new UI and versioning scheme.
Deprecated
- strict_sni_check is now deprecated.
Fixed
- DNS64 treating unresolved CNAME/DNAME answers as the end of resolution chain (#7514).
- Blocked requests without an EDNS(0) OPT record (#8183).

As with everything in life, the best things are only the best because they stand out from the mundane. Without regular there would be no exceptional.
…all these words to say that this AdGuard Home update is the ‘boring’ one, with mostly bug fixes and security updates — so that the next time we add something new, it would feel fresh and exciting!
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.74 GitHub milestone.
Security
• Frontend libraries has been updated to prevent the possibility of exploiting the vulnerability described in CVE-2026-40175.
• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.2.
Changed
Configuration changes
In this release, the schema version has changed from 33 to 34.
• Added a new field doh in http configuration.
# BEFORE:
'http':
# …
'tls':
# …
'allow_unencrypted_doh'：false
# AFTER:
'http':
# …
'doh':
'insecure_enabled'：false
'routes':
• 'GET /dns-query'
• 'POST /dns-query'
• 'GET /dns-query/{ClientID}'
• 'POST /dns-query/{ClientID}'
'tls':
# …
To roll back this change, set the schema_version back to 33.
Fixed
• Incorrect forwarding of root domain requests when domain-specific upstreams are configured (#7058).
• The strict SNI check setting is not persisted when the TLS configuration is changed (#8327).
• Status reported by the launchd service implementation in cases of scheduled service restart.
• Fixed clients block/unblock when moving clients between allowed and disallowed lists.

As with everything in life, the best things are only the best because they stand out from the mundane. Without regular there would be no exceptional.
…all these words to say that this AdGuard Home update is the ‘boring’ one, with mostly bug fixes and security updates — so that the next time we add something new, it would feel fresh and exciting!
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.74 GitHub milestone.
Security
- Frontend libraries has been updated to prevent the possibility of exploiting the vulnerability described in CVE-2026-40175.
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.2.
Changed
Configuration changes
In this release, the schema version has changed from 33 to 34.
- Added a new field doh in http configuration.
# BEFORE:
'http':
# …
'tls':
# …
'allow_unencrypted_doh': false
# AFTER:
'http':
# …
'doh':
'insecure_enabled': false
'routes':
- 'GET /dns-query'
- 'POST /dns-query'
- 'GET /dns-query/{ClientID}'
- 'POST /dns-query/{ClientID}'
'tls':
# …
To roll back this change, set the schema_version back to 33.
Fixed
- Incorrect forwarding of root domain requests when domain-specific upstreams are configured (#7058).
- The strict SNI check setting is not persisted when the TLS configuration is changed (#8327).
- Status reported by the launchd service implementation in cases of scheduled service restart.
- Fixed clients block/unblock when moving clients between allowed and disallowed lists.

We are releasing this hotfix to address a recently discovered critical vulnerability that could allow users to bypass authentication and gain full access to AdGuard Home without valid credentials. We strongly recommend updating your AdGuard Home clients immediately.
Acknowledgments
A special thanks to @mandreko for reporting the vulnerability, our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.73 GitHub milestone.
Security
- Authentication is now applied to requests that have been upgraded from HTTP/2 Cleartext (H2C) requests to public resources.
NOTE: We thank @mandreko for reporting this security issue.

The first release of the year is always important — it sets the tone for the months ahead 📆
The way we kick things off in 2026 may not be flashy, but it’s a solid mix: the new way of handling TLS certificate updates, a couple of other, minor new features, some configuration changes, a couple of key fixes, and the usual security update.
Stay tuned for more goodies to come!
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.72 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.7.
Added
- AdGuard Home now tracks the TLS certificate and key files for updates and reloads them after any updates are detected (#3962).
- New query parameter recent in GET /control/stats/ defines statistics lookback period in millieseconds. See openapi/openapi.yaml for details.
- New field "ignored_enabled" in GetStatsConfigResponse or GetQueryLogConfigResponse. See openapi/openapi.yaml for details.
Changed
- In addition to modifying the contents of a hosts file, deleting or renaming the file now also updates runtime clients and DNS filtering results.
Configuration changes
In this release, the schema version has changed from 32 to 33.
- Added a new boolean field ignored_enabled in querylog and statistics config.
# BEFORE:
'querylog':
# …
'ignored':
- '|.^'
'statistics':
# …
'ignored':
- '|.^'
# AFTER:
'querylog':
# …
'ignored':
- '|.^'
'ignored_enabled': true
'statistics':
# …
'ignored':
- '|.^'
'ignored_enabled': true
```
To roll back this change, set the `schema_version` back to `32`.
Fixed
- Executable permissions in some Docker installations (#8237).
- Unknown blocked services from both global and client configuration now logged instead of causing server crash.

As it turns out, our changes to optimistic DNS cache in the previous update were a little too optimistic, and we’ve broken it a little bit in the process. This hotfix brings everything back to normal, and, as a bonus, we’re adding new settings for users to manually set the upper age limit and TTL for optimistic cache’s stale answers.
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.71 GitHub milestone.
Changed
• Stale records in optimistic DNS cache now have an upper age limit controlled by dns.cache_optimistic_max_age. The default value is 12 hours.
• TTL for stale answers from optimistic DNS cache is now controlled by dns.cache_optimistic_answer_ttl. The default value is 30 seconds.
Configuration changes
In this release, the schema version has changed from 31 to 32.
• Added a new string fields dns.cache_optimistic_answer_ttl and dns.cache_optimistic_max_age.
# BEFORE：
'dns'：
'cache_enabled'：true
'cache_optimistic'：true
# …
# AFTER：
'dns'：
'cache_enabled'：true
'cache_optimistic'：true
'cache_optimistic_answer_ttl'：'30s'
'cache_optimistic_max_age'：'12h'
# …
To roll back this change, set the schema_version back to 31.
Fixed
• Optimistic DNS cache not working (#8148).

Even when the update we roll out is on the smaller side, we still aim for some diversity in the changelog. A little bit of vulnerability shore-ups, a smidge of bug fixes, a new thing or two, and a couple generic changes — a tried and tested recipe for a good, solid update 🧑‍🍳
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.70 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.5.
Added
- New field "start_time" in the GET /control/status response.
Changed
- Stale records in optimistic DNS cache now have an upper age limit of 12 hours.
- New blocked services UI.
Fixed
- Generated mobileconfig could not be installed on macOS 26.1.

AdGuard Home v0.107.69 is here — just a quick pit stop to fix two pesky bugs that tried to sneak past us. No new features this time, but everything should now run a bit smoother (and those bugs have been shown the door).
Full changelog
See also the v0.107.69 GitHub milestone.
Changed
- Node.js 24 is now used to build the frontend.
Deprecated
- Node.js 20 and 22 support.
Fixed
- DHCP settings could not be saved (#8075).
- DNS Rewrite edit modal did not populate with the correct values (#8072).
Removed
- The outdated querylog anonymization script.

Let's get “the usual” out of the way: we’ve made some security updates, as we always do, and even managed to make do without any bug fixes this time, for better or for worse. But let’s focus on the main course: new option to enable and disable DNS rewrite rules 🚦
This was one of the earlier feature requests, and we are happy to finally deliver. You can enable and disable DNS rewrite rules all at once or do so on an individual rewrite basis — both by editing YAML files or via UI.
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.68 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.3.
Added
- New DNS rewrite settings endpoints GET /control/rewrite/settings and PUT /control/rewrite/settings/update (#1765). See openapi/openapi.yaml for details.
- New fields "groups" and "group_id" added to the HTTP API (GET /control/blocked_services/all). See openapi/openapi.yaml for the full description.
Changed
- POST /control/rewrite/add and PUT /control/rewrite/update now accept the optional field "enabled" (#1765). See openapi/openapi.yaml for details.
Configuration changes
In this release, the schema version has changed from 30 to 31.
- Added a new boolean field filtering.rewrites_enabled to globally enable/disable DNS rewrites.
- Added a new boolean field enabled for each entry in filtering.rewrites to toggle individual rewrites.
# BEFORE:
'filtering':
'rewrites':
- 'domain': test.example
'answer': 192.0.2.0
# …
# AFTER:
'filtering':
'rewrites_enabled': true
'rewrites':
- 'domain': test.example
'answer': 192.0.2.0
'enabled': true
# …
To roll back this change, set schema_version back to 30.

Some would call this update small — we prefer the term compact. A new DNS filter, some bug fixing, some optimization — what more can a man ask for? Short and sweet 🍰
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.67 GitHub milestone.
Added
- The HaGeZi's DNS Rebind Protection filter for protecting against DNS rebinding attacks (#102).
- Support for configuring the suggested default HTTP port for the installation wizard via the ADGUARD_HOME_DEFAULT_WEB_PORT environment variable (useful for vendors).
Changed
- Optimized matching of filtering rules.
Fixed
- Excessive configuration file overwrites when visiting the Web UI and a non-empty language is set.
- Lowered the severity of log messages for failed deletion of old filter files (#7964).

You may have the best software in the world, but if people can't access it, it's as good as useless. This is why in today's update we made it a priority to fix a couple of authentication errors — so that you can always log in and use AdGuard Home to its fullest. Couple it with the usual security updates and a pinch of other changes, and you have v0.107.66 on your hands! 🙌
Acknowledgments
A special thanks to our open-source contributor @bakito, our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.66 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.1.
Changed
- Our snap package now uses the core24 image as its base.
- Outgoing HTTP requests now use the User-Agent header AdGuardHome/v0.107.66 (where v0.107.66 is the current version) instead of Go-http-client/1.1 (#7979).
Fixed
- Authentication errors in the Web UI when AdGuard Home is behind a proxy that sets Basic Auth headers (#7987).
- The HTTP API GET /control/profile endpoint failing when no users were configured (#7985).
- Missing warning on the Encryption Settings page when using a certificate without an IP address.

This release contains an assortment of changes, most of which are related to DNS cache — check out the changelog for details. Of course, we have also improved the security as usual by updating the Go version. 🔐
Acknowledgments
A special thanks to our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.65 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.6.
Added
- A separate checkbox in the Web UI to enable or disable the global DNS response cache without losing the configured cache size.
- A new "cache_enabled" field to the HTTP API (GET /control/dns_info and POST /control/dns_config). See openapi/openapi.yaml for the full description.
Changed
Configuration changes
In this release, the schema version has changed from 29 to 30.
- Added a new boolean field dns.cache_enabled to the configuration. This field explicitly controls whether DNS caching is enabled, replacing the previous implicit logic based on dns.cache_size.
# BEFORE:
'dns':
# …
'cache_size': 123456
# AFTER:
'dns':
# …
'cache_enabled': true
'cache_size': 123456
To roll back this change, set the schema_version back to 29.
Fixed
- Disabled state of Top clients action button in web UI (#7923).

Unlike with chickens and eggs, with bugs and bugfixes, unfortunately, the bugs always come first. At least the new update is here to fix them all! 🥚 🐔
Today we have bugfixes for every taste: security bugfixes, cache responses TTL bugfixes, even DNSCrypt certificates bugfixes. And you don't even have to choose — you can have them all with this new version of AdGuard Home.
Acknowledgments
A special thanks our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.64 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.5.
Fixed
- TTL override calculation (#7903).
- Validation process for DNSCrypt settings (#7856).

It’s not always the big issues: sometimes what you need is a few fixes and tweaks to pump up the overall stability 🔩
Acknowledgments
A special thanks our community moderators team and to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
See also the v0.107.63 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.4.
Fixed
- The hostnames of DHCP clients with multiple labels not being recognized.
- Status reported by the systemd service implementation in cases of auto-restart after a failed start.

Many claim to be client-oriented; we're proud to say that AdGuard Home is $client-oriented, as in this update we've fixed (among others) the bug that prevented the rules containing the client modifier from working. 👥
We have also improved AdGuard Home's security by updating the Go version to shore up some vulnerabilities, as usual.
Full changelog
See also the v0.107.62 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.3.
Fixed
- Clients with CIDR identifiers showing zero requests on the Settings → Client settings page (#2945).
- Command line option --update when the dns.serve_plain_dns configuration property was disabled (#7801).
- DNS cache not working for custom upstream configurations.
- Validation process for the DNS-over-TLS, DNS-over-QUIC, and HTTPS ports on the Encryption Settings page.
- Searching for persistent clients using an exact match for CIDR in the POST /clients/search HTTP API.
- Rules with the client modifier not working (#7708).

What's worse than food poisoning? Cache poisoning, of course! In this update, we have fixed the vulnerability that was making AdGuard Home susceptible to cache poisoning attacks.
Acknowledgements
A special thanks to Xiang Li for reporting the vulnerability, our community moderators team, 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.61 GitHub milestone.
Security
- Any simultaneous requests that are considered duplicates will now only result in a single request to upstreams, reducing the chance of a cache poisoning attack succeeding. This is controlled by the new configuration object pending_requests, which has a single enabled property, set to true by default.
NOTE: It's strongly recommended to leave it enabled, otherwise AdGuard Home will be vulnerable to untrusted clients.

If you are reading through these release notes, you must be a true power user of AdGuard Home, as this update isn’t the most flashy one. There are no exciting new features, but there are patches to Go vulnerabilities, UI and docker updates, and a couple of bugfixes.
Full changelog
See also the v0.107.60 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.2.
Changed
- Alpine Linux version in Dockerfile has been updated to 3.21 (#7588).
Deprecated
- Node 20 support, Node 22 will be required in future releases.
NOTE: npm may be replaced with a different tool, such as pnpm or yarn, in a future release.
Fixed
- Filtering for DHCP clients (#7734).
- Incorrect label on login page (#7729).
- Validation process for the HTTPS port on the Encryption Settings page.
Removed
- Node 18 support.

This hotfix addresses the bug that was introduced with the previous update, namely the bug that prevented users from entering anything into the search box in the Query log. We also took this opportunity to include another fix for the incorrect functioning of the client modifier.
Acknowledgments
A special thanks to our community moderators team, @AdguardTeam/community-moderators, 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.59 GitHub milestone.
Fixed
- Rules with the client modifier not working (#7708).
- The search form not working in the query log (#7704).

Here’s a philosophical question for you: if a release contains more bugfixes than usual, is it good or is it bad? 🤔
Luckily, we are developers and not philosophers, so let’s state some facts and leave thought experiments to those wiser than us. And the facts are, we've fixed a bunch of bugs in this update, but also added a neat little feature that we'd like to elaborate on.
An improved tool to check DNS queries
If you are serious about protecting your privacy and dealing with ads, chances are you have loads of rules, both as filter lists and as parts of a custom ruleset. Now, any time you're tweaking your filter arsenal, there is an easy way to check if a certain DNS query will be blocked. We've built upon the already-existing tool and added options to indicate DNS record type and specific client, either by IP address or by ClientID. Enter the information and behold all the rules that match your request. Bonus feature: you can unblock any domain right then and there. Happy blocking!
Screenshot at 2025-03-19 17-37-17
Acknowledgments
A special thanks to our open-source contributors: @bankjirapan, @dervomsee, and @viraniac, our community moderators team, 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.58 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.1.
Added
- The ability to check filtering rules for host names using an optional query type and optional ClientID or client IP address (#4036).
- Optional client and qtype URL query parameters to the GET /control/check_host HTTP API.
Fixed
- Clearing the DNS cache on the DNS settings page now includes both global cache and custom client cache.
- Invalid ICMPv6 Router Advertisement messages (#7547).
- Disabled button for autofilled login form.
- Formatting of elapsed times less than one millisecond.
- Changes to global upstream DNS settings not applying to custom client upstream configurations.
- The formatting of large numbers in the clients tables on the Client settings page (#7583).

The year 2025 is only picking up steam, but some of us already need a time out 🕙 Speaking of timeouts, in the new version we've added the ability to specify the upstream timeout in the Web UI, alongside with some bug fixes and security updates.
Acknowledgments
A special thanks to our open-source contributor @janpieper, our community moderators team, 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.57 GitHub milestone.
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.6.
Added
- The ability to specify the upstream timeout in the Web UI.
Changed
- The Fastest IP address upstream mode now correctly collects statistics for all upstream DNS servers.
Fixed
- The hostnames of DHCP clients not being shown in the Top clients table on the dashboard (#7627).
- The formatting of large numbers in the upstream table and query log (#7590).

We are steadily picking up the pace in the new year, starting with this small update. 🏃 Inside are some fresh bugfixes, a new API, and an updated Go version to shore up some vulnerabilities.
Acknowledgments
A special thanks to our open-source contributor @Hermholtz, our community moderators team, 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 Go vulnerabilities fixed in 1.23.5.
Added
- The new HTTP API POST /clients/search that finds clients by their IP addresses, CIDRs, MAC addresses, or ClientIDs. See openapi/openapi.yaml for the full description.
Deprecated
- The GET /clients/find HTTP API is deprecated. Use the new POST /clients/search API.
Fixed
- Request count link in the clients table (#7513).
- The formatting of large numbers on the dashboard (#7329).

After the last update it became possible for banned users to make DNS queries over encrypted protocols. This behavior, of course, was not intended, and is fixed by this hotfix.We apologize for this oversight and will do our best to avoid repeating such mistakes in the future.Full changelog
See also the v0.107.48 GitHub milestone.Fixed
- Access settings not being applied to encrypted protocols (#6890)

Another security and bug fix update, but this time we also fix a :clock3: time zone selection issue and a few other annoying bugs!Acknowledgements
A special thanks to our community moderation team, @AdguardTeam/community-moderators, 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.47 GitHub milestone.Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in Go 1.22.2.
Changed
- Time Zone Database is now embedded in the binary (#6758).
- Failed authentication attempts show the originating IP address in the logs, if the request came from a trusted proxy (#5829).
Deprecated
- Go 1.22 support. Future versions will require at least Go 1.23 to build.
- Currently, AdGuard Home uses a best-effort algorithm to fix invalid IDs of filtering-rule lists on startup. This feature is deprecated, and invalid IDs will cause errors on startup in a future version.
- Node.JS 16. Future versions will require at least Node.JS 18 to build.
Fixed
- Resetting DNS upstream mode when applying unrelated settings (#6851).
- Symbolic links to the configuration file begin replaced by a copy of the real file upon startup on FreeBSD (#6717).
Removed
- Go 1.21 support.

As promised in the notes for the previous release, this update brings some quality-of-life improvements as well as a few bug fixes :wrench:.Full changelog
See also the v0.107.46 GitHub milestone.Added
- Ability to disable the use of system hosts file information for query resolution (#6610).
- Ability to define custom directories for storage of query log files and statistics (#5992).
Changed
- Private rDNS resolution (dns.use_private_ptr_resolvers in YAML configuration) now requires a valid "Private reverse DNS servers", when enabled (#6820).NOTE: Disabling private rDNS resolution behaves effectively the same as if no private reverse DNS servers provided by user and by the OS.
Fixed
- Statistics for 7 days displayed by day on the dashboard graph (#6712).
- Missing "served from cache" label on long DNS server strings (#6740).
- Incorrect tracking of the system hosts file's changes (#6711).

This is a small release containing a security update, a few fixes, and a small feature. More to come soon!Acknowledgements
A special thanks to our open-source contributors, @hoang-rio, 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.45 GitHub milestone.Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in Go 1.21.8.
Added
- Context menu item in the Query Log to add a Client to the Persistent client list (#6679).
Changed
- Starting with this release our scripts are using Go's forward compatibility mechanism for updating the Go version.Important note for porters: This change means that if your go version is 1.21+ but is different from the one required by AdGuard Home, the go tool will automatically download the required version.If you want to use the version installed on your builder, run:

go get go@$YOUR_VERSION
go mod tidy

and call make with GOTOOLCHAIN=local.
Deprecated
- Go 1.21 support. Future versions will require at least Go 1.22 to build.
Fixed
- Missing IP addresses in logs when querying for domain names from the ignore lists.
- Blank page after resetting access clients (#6634).
- Wrong algorithm for caching bootstrapped upstream addresses (#6723).
Removed
- Go 1.20 support, as it has reached end of life.

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

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