Long time ago scientists discovered an interesting phenomenon. While we typically think that what we most want is to actually get what we want, the most intense source of pleasure is in looking forward to getting what we want. That's the dopamine system, also known as the wanting system.
It's been months since Apple added native DNS encryption support to iOS and you might've thought that we at AdGuard just have been lazy not adding support too? Not at all! We've just been trying to follow science and provide you with as much pleasure as possible. Finally, the intensification period ends and catharsis begins!
Native support for encrypted DNS #1589
So in 2020 Apple platforms started natively supporting encrypted DNS. Namely, two protocols were supported — DNS-over-TLS and DNS-over-HTTPS (DoT and DoH). Earlier you could set up and manage DNS profiles in AdGuard. Yet, the solution wasn’t so snorky. Now we've made things simple: there is no need to download and install DNS profiles, just enable Native implementation in AdGuard for iOS settings:
The new method of setting up DNS isn't really superior to the one you're already familiar with, but it has one slight advantage: the DNS is handled by the system and not the app. This means that AdGuard doesn't have to create a local VPN. Sadly, this will not help you circumvent system restrictions and use AdGuard alongside other VPN-based applications — if any VPN is enabled, native DNS is ignored. Consequently, you won't be able to filter traffic locally or to use our brand new DNS-over-QUIC protocol (DoQ)
Now the Google login widget is present in the app (AdGuard > Settings > License > Login). A single click on a Google Sign-in button, and you're there!
For a successful login, you should have an AdGuard account registered to your Google email address. Otherwise, there will be an error.
Don't have an AdGuard account? Create one at my.adguard.com
first, then you'll be able to bind it to your Google account.
Low-level stuff. ☢ For geeks only!! 🤓
Blocking mode, Block IPv6, Blocked response TTL, Bootstrap and Fallback servers — all settings on this screen are new, except for the Tunnel mode.
Bootstrap and Fallback
Fallback is simply a backup DNS server. If you chose a DNS server and something happened to it (whatever the reason), a fallback is needed to set the backup DNS server until the main server responds.
With Bootstrap, it’s a little more complicated. For AdGuard for iOS to use a custom secure DNS server, our app needs to get its IP address first. For this purpose, the system DNS is used by default, but sometimes this is not possible for various reasons. In such cases, Bootstrap could be used to get the IP address of the selected secure DNS server. Here are two examples to illustrate when a custom Bootstrap server might help:
When a system default DNS server does not return the IP address of a secure DNS server and it is not possible to use a secure one.
When our app and third-party VPN are used simultaneously and it is not possible to use System DNS as a Bootstrap.
Block IPv6 🔒 #1289
For any DNS query sent to get an IPv6 address, our app returns an empty response (as if this IPv6 address does not exist). Now there is an option not to return IPv6 addresses.
Does anybody actually read these? ┬──┬ ノ( ゜-゜ノ)
[Fixed] AdGuard shows DNS requests although disabled #1667
[Fixed] VPN restarts when entering the app #1709
[Enhancement] Intercept abp:subscribe and subscribe.adblockplus.org URLs #27
[Other] Updated DnsLibs to 1.4.33