Updates AdGuard 4.1 for iOS: native DNS support and new low-level settings

Gandalf_The_Grey

Level 45
Verified
Trusted
Content Creator
Apr 24, 2016
3,420
Native DNS support
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 current of pleasure lies in looking forward to getting what we want. 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 it? Well, 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!

So yeah, the most important thing this release features is native DNS support.

As you may remember, we already wrote that Apple started natively supporting encrypted DNS. Namely, two protocols were supported — DNS-over-TLS and DNS-over-HTTPS (DoT and DoH correspondingly). In that post we added a manual on how to set up and manage DNS profiles in AdGuard. Yet, the solution wasn’t so elegant.

In the new version, there are already three protocols supported (Regular DNS as well) and the method has become native not only to the iOS, but also to AdGuard. We have simplified the scheme: now you don’t need to download and install DNS profiles, it would suffice to enable Native implementation in AdGuard for iOS settings.
  1. Open AdGuard Settings > DNS protection > DNS implementation > Switch to Native.
  2. Toggle on DNS protection. You’ll see an instruction saying what to do next (Open System settings, go to General > VPN & Network > DNS and select AdGuard there).
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).
 

Gandalf_The_Grey

Level 45
Verified
Trusted
Content Creator
Apr 24, 2016
3,420
Other AdGuard updates:
We've updated AdGuard for Mac, AdGuard for Android and AdGuard Home — and they all are mostly about bugfixes and 'polishing'. In case of AdGuard Home, the socks are even extra soft and have a real nice ornament, but more about it later.

The changelog of AdGuad v2.5.2 for Mac is meat and potatoes. It features the routine CoreLibs update that will move the overall filtering quality just a notch higher, some bugfixes, including dealing with a quite nasty crash. Oh, the Browser Assistant extension will now work in Edge! We also have some good news for our Dutch users: AdGuard is now fully tranlsated into Dutch! Graag gedaan!
Important! Starting with this update, AdGuard will only work on macOS 10.12+. Unfortunately, the older macOS versions do not have capabilities to support the advanced techniques we use in our filtering engine.

With AdGuard v3.6.1 for Android the story is very similar. The most notable thing about this update is that it acts as the first stepping stone towards v4.0 — there will probably be no v3.7.

And the changelog is all the usual suspects: CoreLibs update, a bug fixed here, a bug fixed there. Next!

The most intriguing of the three is the AdGuard Home v0.105.0 update. Prepare to activate your inner nerd if you're going to check out what's new: there's enough IT slang to scare away an average user. But if you're interested in AdGuard Home, presumably you know what you're getting yourself into, and in that case the new version has some goodies in store for you.
Among the major new features are:
  • Client ID support for DoH, DoT and DoQ
  • New powerful modifiers $dnsrewrite and $dnstype
  • An option to set up AdGuard Home as a DNScrypt resolver
While we were preparing this post, a hotfix was released. You can read about changes in v0.105.1 here.
 
Top