Network-wide ads & trackers blocking DNS server
As the winter holidays approach, many of us begin to think about what gifts we will give and receive :gift:. 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.
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!
See also the v0.107.42 GitHub milestone.
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).
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.
ipset entries family validation (#6420).
Pre-filling the New static lease window with data (#6402).
Protection pause timer synchronization (#5759).
Changes compared to the previous beta, v0.108.0-b.49. See CHANGELOG.md for all changes.
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!
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).
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.
ipset entries family validation (#6420).
Pre-filling the New static lease window with data (#6402).
Protection pause timer synchronization (#5759).
Changes compared to the previous beta, v0.108.0-b.48. See CHANGELOG.md for all changes.
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!
See also the [v0.107.41 GitHub milestone][ms-v0.107.41].
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).
Increased the height of the ready-to-use filter lists dialog (#6358).
Improved logging of authentication failures (#6357).
dns.ratelimit_subnet_len_ipv4 and dns.ratelimit_subnet_len_ipv6 have been added to the configuration file (#6368).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).
Bugs are as certain as the change of the seasons :calendar:. 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!
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!
See also the v0.107.41 GitHub milestone.
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).
Increased the height of the ready-to-use filter lists dialog (#6358).
Improved logging of authentication failures (#6357).
dns.ratelimit_subnet_len_ipv4 and dns.ratelimit_subnet_len_ipv6 have been added to the configuration file (#6368).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).
What could be spookier than bugs preventing people from using their networks :ghost:? Luckily, we're here to bust them with this hotfix release!
See also the v0.107.40 GitHub milestone.
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).
Changes compared to the previous beta, v0.108.0-b.47. See CHANGELOG.md for all changes.
Changes compared to the previous beta, v0.108.0-b.46. See CHANGELOG.md for all changes.
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).
ipset entries are updated more often (#6233).
Node.JS 16 is now required to build the frontend.
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).
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!
See also the v0.107.39 GitHub milestone.
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).
ipset entries are updated more often (#6233).
Node.JS 16 is now required to build the frontend.
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).
Changes compared to the previous beta, v0.108.0-b.45. See CHANGELOG.md for all changes.
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.
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.
See also the v0.107.38 GitHub milestone.
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.