iOS AG Pro and NextDNS.
I have a technical question for those who are using NextDNS within iOS Adguard Pro.
If AG Pro is implemented as a fake VPN and use NextDNS as DNS
1. Does AG application log shows DNS queries and NextDNS shows what AG didn't catch?
Or
2. Does the query goes directly to NextDNS first and AG log just shows what NextDNS didn't catch?
Also, using AG Native implementation doesn't show NextDNS QUIC option for some reason I don't know.
4 replies
-
#1 is most accurate. AdGuard will filter based on the filter lists you have installed then will use NextDNS as the resolver for things that it did not block.
iOS does not support DoQ natively so in order to use DoQ, AdGuard has to use the VPN profile. iOS does support DoH natively which is why that works with the native configuration.
-
I have been wondering the same thing. I am using NDNS+Adguard Pro. In my experience, I'll reset everything to zero in both AG & NDNS, and not even 10min of browsing, AG shows over 1,000 ads blocked, and NDNS shows under 100 blocked.
-
Yeah no QUIC option. It doesn’t seem to run DoH3 either which would give you greater benefits since it includes the QUIC protocol.
Content aside
-
1
Likes
- 1 yr agoLast active
- 4Replies
- 258Views
-
4
Following