polewallstar.blogg.se - Adguard dns ios

And with the growth of IOT, those blind spots were proliferating rapidly. AdGuard Ad Blocker had already been launched on every platform where it could be run, but it still had some blind spots. Warning: This is a very technical post aimed at engineers and their supporters. But when we just started it was not so rosy.

90% of these requests are encrypted protocols (DNS-over-TLS, DNS-over-HTTPS, DNS-over-QUIC).īy the numbers, you can tell that this is a very serious workload, and I think we've coped with it pretty well.

It processes more than 1,000,000 DNS requests per second from over 50 million users.

It's deployed on dozens of servers worldwide.

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. We hope that what we're doing can be useful to others and we can therefore contribute to further development of DNS.Īt this point, we could just provide a link to our repo, but that would be boring and uninteresting. Second, we feel like we've done a good job and we'd love to share the results with the open source community.

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. Why are we doing that? There are several reasons for this decision.įirst, it's essential for us that AdGuard DNS users trust us and see exactly what the server is doing. 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).

AdGuard DNS has always been an open-source project in accordance with our policy (all our free products are open source).īut 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.