iOS only lets one VPN (packet tunnel) run at a time. So if you use a WireGuard VPN (Proton, Mullvad, your own server), you can't also run a local filtering app next to it. Most people end up putting a blocking DNS (NextDNS, AdGuard DNS) in the WG config, or relying on the provider's built-in blocking.
I'm the developer of ADFastDNS, an iOS/macOS app that does local DNS filtering (custom wildcard rules, allowlists) plus some network intrusion detection. I'm considering letting it run in front of a WireGuard config you import: the filtering happens on-device, and then your traffic goes out through your VPN.
Before I spend months on it, I'd like to know if this is a real problem for anyone:
- Do you use a WireGuard VPN on iOS together with a DNS/ad blocker today? How?
- What's missing or annoying in that setup (custom rules, per-domain control, logs, DNS leaks)?
- Would you use something like this, or is the DNS= line in the config enough for you?
I'm not selling anything here, just trying to find out if this is worth building.
Happy to answer questions about how it would work.