AdGuard DNS -versiot
In AdGuard DNS v2.1.2 we’ve enhanced the dashboard interface, added a server in Johannesburg and an option to disable automatic filtering log updates. Also, we’ve fixed some bugs so it will no longer be a problem to rename the device or understand the statistical report.
If you use AdGuard VPN for Android or iOS, you can easily add an encrypted DNS to your device. Just follow our instructions when adding a new device.
Option to disable automatic filtering log updates #264
Turkish language support
This hotfix is intended to correct minor errors and add two localizations as a bonus.
AdGuard DNS now supports DNS-over-HTTP/3 in experimental mode. It was a challenge, but we made it. For now only AdGuard Home and dnsproxy fully support DNS-over-HTTP/3, but soon DoH3 will appear in other AdGuard products. However, we focus on DNS-over-QUIC and consider it more advanced, but we strive to support the other protocols too, and DoH3 is a proof of that.
Another good news is that we will email AdGuard DNS users weekly and monthly reports with stats on requests, devices, and companies, which is convenient and visual. If there are too many reports, you can unsubscribe at any time.
[Enhancement] Added the Apply button that appears after changing the server name
[Enhancement] Query log data cutoff in desktop mode #366
[Enhancement] Query log page numbers move when a new page is opened #368
[Fixed] Switching from 90 days to anything less causes dates to overlap #323
[Fixed] Text is cut off for the last domain in Top domains #339
[Fixed] Dates are cut off on the left and right side of the chart (mobile version of the website) #341
[Fixed] Misleading subscription status (from AdGuard VPN) #352
[Fixed] Wrong status of applied unblocking rules #361
[Fixed] The "Refresh" button on the homepage does not override the number of requests
[Fixed] Query log data is cut off (desktop version of the website) #366
[Fixed] Limit triggering in Enterprise plan
[Fixed] Can't scroll to account settings on Safari for macOS #353
[Fixed] In some cases the statistics were counted incorrectly
[Fixed] Top Destinations stats overlap when set to 90 days #326
It's been two weeks since the release of AdGuard DNS 2.0, but there's still a pleasant aftertaste. We've been painstakingly working on this product to give you a reliable and convenient tool to control your online traffic. And we succeeded.
Still, small bugs had crept into the release. That's why we're publishing a patch today: so you can enjoy the service, and we can move on to some bigger tasks with peace of mind.
[Enhancement] Added search to the DNS knowledge base
[Enhancement] Updated link for Contact Us button on purchase page
[Enhancement] Improved the Traffic Destinations page
[Enhancement] Add an option to use
add-cpe-idin Dnsmasq to identify the device
[Fixed] Disabling logs disables tariff statistics
[Fixed] Numbers in Japanese, Korean, Chinese are displayed incorrectly
The beta testing phase is finally over! From now on the new level of traffic control is available for you. With AdGuard DNS 2.0 you can:
Flexibly configure domain blocking via blocklists, query log and user rules;
See real-time requests statistics from all connected devices;
Enable and set up Parental control;
Choose one of four subscription plans that suits you most.
Learn more about all the changes and improvements of AdGuard DNS 2.0 in our blog.
Check out the sixth beta version of AdGuard DNS (and hopefully the final one before the release). In it we’ve improved the dark theme: updated the map styles and QR-code, so that everything could be easily read and scanned. And, of course, we fixed some minor bugs. The private AdGuard DNS now runs smoother!
[Enhancement] Updated map styles in the dark theme
[Enhancement] Added an option to disable iCloud Private Relay
[Fixed] QR code is not scanned in the dark theme
[Fixed] Autofill doesn’t work in Safari on macOS and iOS
[Fixed] Minor bug fixes in desktop и mobile versions
There are five fingers in a hand, five oceans on Earth, and five betas of the private AdGuard DNS. Today we're releasing the fifth beta of our DNS and we hope you'll rate it 5/5!
In this version we’ve implemented support for DDR (Discovery of Designated Resolvers) by the latest draft of the new standard. With this feature, an encrypted connection to the DNS server will be set up automatically on devices with DDR support, provided the device previously knew the server address. A computer or smartphone will send a request to the known address and receive all the necessary information to establish a secure connection.
DDR support appeared in Windows 11 Insider Preview Build 22489, which means that the feature will get into the release version after a while. When this happens, Windows and AdGuard DNS users will be automatically reconnected to encrypted DNS servers – public or private, depending on the services selected earlier.
We’ve also improved ECS (EDNS Client Subnet) implemented in the third beta. Servers now respond with more precise IP addresses that better match your location. Furthermore, we are continuing to refine the open AdGuard DNS API, and now there are methods for getting statistics. All documentation is available at Knowledge Base.
We’ve fixed some bugs and worked on the interface: authorization via Apple ID now works properly, the dark theme has become really dark, and the Query log is prettier than ever. French, Italian, Chinese, Japanese, and Korean were added to the dashboard, and we are committed to continue localizing the private AdGuard DNS, making it accessible to users from all over the world!
[Enhancement] Added support for DDR (Discovery of Designated Resolvers)
[Enhancement] Statistic retrieval methods were added to the API
[Enhancement] Added an option to change subscription type
[Enhancement] Added an option to extend subscription
[Enhancement] Added support for Chinese, Japanese, Korean, French, and Italian
[Enhancement] Added the "Don’t ask again" checkbox to the system notification that appears when deleting user rules
[Fixed] After logging in via Apple ID the personal account opens instead of dashboard if the user has an AdGuard VPN subscription
[Fixed] In dark theme statistics blocks are highlighted in white
[Fixed] In dark theme text in some fields is grayed out
[Fixed] Some elements in the mobile version of the website are displayed incorrectly
The period of active "building" of the private AdGuard DNS is left behind, and now we're polishing the service to a shine. Just take a look at the current changelog and compare it to the one we published for the previous beta. The difference is obvious.
The fourth beta features dark theme and language selection – at the moment, the dashboard is translated into German, Spanish, and Russian. To find both options, go to Account settings. And some more good news: from now on all AdGuard VPN users with a subscription will get the Personal plan of the private AdGuard DNS for free.
We hope you’ll enjoy the new version. Use the service and leave feedback on any platform you like.
[Enhancement] Added dark theme
[Enhancement] Added support for VPN subscriptions and information about VPN subscribers automatically getting a Personal DNS subscription
[Enhancement] Added German and Spanish localizations
[Enhancement] Improved search function in the filter section on mobile devices
[Enhancement] Supplemented instructions for different devices
[Enhancement] Added a link to DNS rules syntax in the query log dialog
[Fixed] The “View device settings” button doesn't work on iOS devices
[Fixed] The “Unable to renew subscription” popup hangs for too long
The recently released third beta of private AdGuard DNS was really good and brought a lot of useful features to users. However, as it turned out, it contained a few flaws. So that you don't have to deal with them anymore, we are releasing a patch v0.3.1 for private AdGuard DNS.
[Fixed] Clicking the Block button in Query log deletes all existing user rules and replaces them with a new one #265
[Fixed] Unable to move devices between servers #248
[Fixed] Incorrect links on the "Thanks for your purchase" page
[Fixed] Discount promo codes do not work correctly
[Fixed] There is no payment button in the mobile version of the website
[Fixed] Incorrect designation of the number of requests in Statistics
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
To make it easier to understand AdGuard DNS, we've added the Knowledge Base. You can see all the latest Knowledge Base changes in the AdGuard DNS GitHub repository.
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.
We've also fixed DNS filters: eliminated the bug with the
/etc/hosts-stylerules 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.
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.
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”).
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.
[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
We’ve all been waiting for it: we're proud to present the open beta of private AdGuard DNS! From now on, anyone can set up their own DNS server.
We took the best of AdGuard DNS and AdGuard Home and designed a product that would be flexible and customizable, meet the needs of "geeks", and have a user-friendly interface. We hope we succeeded! And now let's take a closer look at the best features of private AdGuard DNS.
With a private DNS server, it is only you who decides which domains should be blocked and which shouldn’t — on each device! Connect your computer, smartphone, tablet or router and manage their requests as desired.
You can also choose which domain blocking rules should be implemented. And those who aren't satisfied with dozens of pre-installed blocklists can import and export their own custom rules.
Now you can see the full statistics of your requests: how many requests were registered, to which companies, and to which countries. Besides, you can view this information for different dates, countries, and even for different devices connected to your DNS server. And of course, block and unblock requests on the go.
To protect your child from online content you deem inappropriate, you can use Parental control. You can activate the safe search and manually specify domains for blocking as well as set the schedule: for instance, not allow your child to watch videos during homework.
Join beta testing
To take part in beta testing go to AdGuard DNS website and press *Join beta***, then sign up or log into your AdGuard account. You're done! Create your own DNS server and manage your requests — you are in control.
Great news: AdGuard DNS is advancing to a new level. We're about to release the product that many have yearned for so long — the private AdGuard DNS!
What a public DNS server blocks cannot be changed — it only has to be taken for granted. With your own DNS server, you'll be in control of all the query statistics and be able to choose which domains you want to block. It'll allow you to add blocklists and set up Parental control. And the user-friendly interface will make it no problem to get to grips with it all.
We added a new website where you can already see what the private AdGuard DNS interface will look like, learn how to connect to the public DNS server, and subscribe to the AdGuard DNS newsletter. If you do, we'll message you at launch and keep you up-to-date with the latest AdGuard news.
Thank you for your support! Stay tuned — and in the meantime, we're working to make sure the next release is to your liking.