AdguardTeam/AdGuardHome v0.107.42

AdGuard Home v0.107.42

on GitHub

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