We recently announced that we've moved to a shorter release cycle for mobile product development — 4–6 weeks instead of 3–6 months. To back up these words, we are releasing a new version of AdGuard for iOS one month after the previous one.

In v4.5.2, we've added basic HTTP authentication for DNS-over-HTTPS, updated DnsLibs and Scriptlets, and fixed minor bugs.

What is basic HTTP authentication and why do you need it?

One of the benefits of DNS-over-HTTPS is that it supports HTTP protocol features. Standard DNS does not provide any kind of authentication, but HTTP does. Having updated DnsLibs to version 2.4, we've added the option of HTTP authentication when configuring a DNS server.

Why do you need authentication in DNS? Imagine you have your own DNS server and you don't want anyone else to use it. Without authentication, the only way to do this would be to configure IP address restrictions manually. For example, you could allow only your home IP address to connect to the DNS server. But what if you use a mobile device and constantly change networks? That's where the HTTP authentication feature in AdGuard for iOS comes in handy. There is a nuance, though — AdGuard Home and AdGuard DNS don't have DNS servers with support for it yet. But they will be available soon, so stay tuned!

We hope you will like the new AdGuard for iOS. The complete list of changes can be found on Github. And if you come up with a new feature you'd like to see in the app, or if you notice a bug, let us know in Issues.