AdGuard Home, the popular ad-blocker, has released its latest version, v0.108.0-b.51. This update brings several improvements and fixes compared to the previous beta, v0.108.0-b.50.

In terms of security, the Go version has been updated to address potential vulnerabilities. This update specifically prevents the exploitation of the CVE-2023-39326, CVE-2023-45283, and CVE-2023-45285 Go vulnerabilities. These vulnerabilities have been fixed in Go 1.20.12, ensuring a more secure experience for users.

One notable addition in this release is the ability to set a client’s custom DNS cache. This feature, requested by users, allows for more personalized DNS caching, enhancing the overall performance and customization options of AdGuard Home.

Furthermore, this update also addresses a memory leak issue when using parallel queries. The fix for this problem, identified as issue #6438, ensures better memory management and stability.

For a complete list of changes and updates in AdGuard Home v0.108.0-b.51, please refer to the CHANGELOG.md file.

AdGuard DNS Proxy has recently released version v0.56.1, which comes with some important fixes. One of the major fixes addresses the issue where queries of DS type were being incorrectly routed to the exactly matched domain-specific upstream. This behavior was in contrast to the recommendations outlined in RFC 4035 Section 2.4.

By releasing this new version, AdGuard DNS Proxy ensures that the routing of DS type queries is now in accordance with the RFC 4035 Section 2.4 recommendations. This fix enhances the overall performance and reliability of the DNS proxy. Users can now have confidence that their queries of DS type will be handled correctly and routed to the appropriate upstream destinations.