NextDNS (the resolver) is not equivalent to using an app (a client) like TrackerControl.

NextDNS (the resolver) cannot prevent apps from doing their own DNS, or prevent apps from connecting to preset IPs. Only if the queries reach the resolver can NextDNS act upon it / track it / block it.

Also, apps like TrackerControl can do per-app blocking, just like LittleSnitch / LuLu and Glasswire do on macOS and Windows respectively.

For some background on what apps like TrackerControl could potentially protect against, see: https://github.com/celzero/rethink-app/issues/301#issuecomme...

Disclosure: I co-develop a FOSS app similar to TrackerControl and a FOSS alternative to NextDNS.

Thanks for the clarification! I didn’t expect apps would be resolving using their own DNS or connecting to preset IPs, but it makes perfect sense.

I’m curious, what’s the FOSS alternative to NextDNS you’re developing?

> I'm curious, what's the FOSS alternative to NextDNS you’re developing?

Well, NextDNS is the gold-standard. We are merely building as much as we can but our motive is to remain serverless, so as to be zero-maintenance.

https://github.com/serverless-dns/serverless-dns

NextDNS won't show you companies behind tracking and where your app sends the data to.