AdguardTeam/AdGuardHome v0.107.58

AdGuard Home v0.107.58

on GitHub

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!

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