Meet the third beta version of private AdGuard DNS! We are steadily moving towards a full-fledged product, adding new features, changing and improving UI — everything to make you really enjoy using AdGuard DNS.
The version history – in front of your eyes
First and foremost, we've added a version history page for the AdGuard DNS service. Now you can see the full list of changes, learn about new features, and see how the work on private AdGuard DNS service is progressing.
Contribute to AdGuard DNS translation
Until now, private AdGuard DNS could only be used in English: first we had to make sure everything was working as it should. With this version we've extended the geography by adding the possibility to translate the dashboard into different languages. Help us make AdGuard DNS more accessible to everyone by participating in the translations! You can find a detailed article on how to use the Crowdin platform in our
Knowledge Base. And if you already know how to use it, visit the
AdGuard DNS project in Crowdin. Select the Dashboard and choose the language you want, then you're ready to translate!
AdGuard DNS Knowledge Base
Subscription
We've added a paid subscription on private AdGuard DNS. Subscription is not required during beta testing, but we'd appreciate it if you'd like to support us now.
DNS filters
We've also fixed DNS filters: eliminated the bug with the
/etc/hosts-style
rules failing to work and added support for rules with
$dnsrewrite
. By the way, you can read about the
DNS filtering syntax in the Knowledge Base.
ECS support
The AdGuard DNS servers now support EDNS Client Subnet (ECS).
This feature allows users to get responses corrected for the location of the DNS user. We had long been hesitating to implement it in AdGuard DNS: ECS assumes handing over an anonymized user's IP address to the name server. In this version, we've solved the problem: instead of the user's IP address, we pass another address from approximately the same location as the user's.
New blocklists
We've added a lot of new blocklists — now it's even easier to customize AdGuard DNS. And if that's not enough, you can request and add more blocklists in the
GitHub repository (before you do that, read requirements for blocklists in the section
“What Blocklists Can Be Added Here”).
Open API
AdGuard DNS now has an open API. If you want to integrate with AdGuard DNS, read the
documentation.
UI fixes and more
We've also fixed a lot of minor bugs and added some useful features.
Test private AdGuard DNS and leave feedback on any convenient platforms — it will help us become better.
Changelog
[Enhancement] Improved the appearance of the multiselect (element with the ability to select multiple values, such as countries, devices)
[Enhancement] For the device location, the Traffic Destination section uses data from its last activity
[Fixed] Incorrect detection for account time zone
[Fixed] Statistics and logs do not get cleared when their retention period is changed
[Fixed] Incorrect country detection for some domains
[Fixed] Significant delay in clearing logs and statistics
[Other] Added the option "Last 7 days" to date selector