AdGuard DNS has always been an open-source project in accordance with our policy
(all our free products are open source).
But with the release of AdGuard DNS 2.0
, we encountered a problem: on the one hand, this version provides a free public server, but on the other hand, it also has personal server functionality. We figured out what to do for a while, and after all we decided to open the code, but under a fairly strict license (AGPL).
Why are we doing that? There are several reasons for this decision.
First, it's essential for us that AdGuard DNS users trust us and see exactly what the server is doing. One can't just say that we are for all good and against all bad, the community should be able to check, verify and point out mistakes.
Second, we feel like we've done a good job and we'd love to share the results with the open source community. We hope that what we're doing can be useful to others and we can therefore contribute to further development of DNS.
At this point, we could just provide a link to our repo, but that would be boring and uninteresting. So today I'm going to tell you the story of how the AdGuard DNS evolved with time, what drove the changes, and why we made certain architectural decisions.
So what is AdGuard DNS today?
- It's deployed on dozens of servers worldwide
- It processes more than 1,000,000 DNS requests per second from over 50 million users
- 90% of these requests are encrypted protocols (DNS-over-TLS, DNS-over-HTTPS, DNS-over-QUIC).