Skip to content

RethinkDNS: Local DNS and Firewall via Android VPN

RethinkDNS: Local DNS and Firewall via Android VPN

RethinkDNS review: what happens when its local DNS firewall and Android Private DNS are enabled together, plus DoH, DoT, and DNSCrypt resolver choices.

App summary

App
RethinkDNS
Developer
Celzero
License
MPL-2.0
Version
unknown
Size
unknown
Price
Free

RethinkDNS is one of those Android apps that does something genuinely useful and then hands you a control panel with a lot of switches. It is a local DNS resolver, a per-app firewall, and a blocklist-based filter, all delivered through Android’s VPNService by a developer called Celzero. It is free, it is open source under MPL-2.0, and it asks you to make decisions that most ad-blocking apps hide behind a single toggle.

What follows sticks to what the app’s own materials and public listing state. Where the documentation does not answer a question — and there are several — this article says so rather than guessing.

RethinkDNS and Android Private DNS: What Happens When Both Are Enabled

This is the question the documentation does not answer. RethinkDNS runs as a local DNS resolver on top of Android’s VPNService. Android Private DNS is a separate system setting, configured in the phone’s network options, independent of any app. The fact data available for this review does not specify what happens when both are active at the same time, so treat any confident claim about the interaction — including claims that one silently overrides the other — as unverified.

What can be said is that the two are not the same mechanism, and they should not be treated as interchangeable. RethinkDNS supports DNS-over-HTTPS, DNS-over-TLS, and DNSCrypt, and it lets you pick the resolver those queries go to. Android Private DNS is a system-level setting with its own rules about which resolvers it will accept. Because they are configured in different places and enforced by different parts of the OS, enabling one does not automatically configure the other, and there is no documented statement here about precedence.

The routing detail matters for anyone trying to reason about this. RethinkDNS processes DNS traffic on the device or forwards it to the resolver the user selected. That is a description of where queries go, not a description of how Android arbitrates between an app-level resolver and a system-level Private DNS setting. If you care about which resolver actually answers your queries, configure DNS in one place, then check behavior instead of assuming.

Privacy expectations deserve the same caution. Because DNS traffic is either handled locally or sent to a resolver you chose, the meaningful questions are about logs, diagnostics, and any optional telemetry. The fact data explicitly points readers to the official privacy policy for those details, and it does not state whether telemetry or diagnostics are enabled by default. That is an unknown, and it is the kind of unknown worth resolving before you leave the app running permanently.

What the App Actually Does

Three functions are listed: a local DNS resolver with support for encrypted DNS protocols, a per-app firewall that allows or blocks network access, and blocklist-based domain filtering. Those are distinct jobs that happen to share one interface. The resolver decides how DNS queries travel and who answers them. The firewall decides which apps get network access at all. The blocklists decide which domains get refused.

The most common misconception is that RethinkDNS is just another DNS changer. It is not, because the per-app firewall is a separate capability with its own rules and its own connection logs. A DNS changer can only answer queries; it cannot stop an app from opening a socket to a hardcoded IP address. The firewall layer is what makes the app a firewall rather than a resolver with extras.

The second misconception is that blocking app internet access requires root. RethinkDNS implements its firewall through Android’s VPNService, which is the mechanism the fact data describes. That is a standard, non-root approach on Android: the system routes traffic through the app’s local VPN interface, and the app decides what passes. No rooting step appears anywhere in the described design.

The third misconception is that this is a full VPN in the anonymity sense. The fact data describes a local VPNService where DNS traffic is processed on-device or sent to a user-selected resolver. Nothing in the material describes tunneling all app traffic to a remote server for geo-unblocking or identity masking. If you want a commercial VPN, this is a different category of tool that happens to occupy the same Android slot.

And it is not an antivirus or malware scanner. There is no scanning engine in the described feature set. Blocklist filtering refuses domains that appear on lists you enabled; it does not inspect files, judge app behavior, or detect malicious code.

Encrypted DNS: DoH, DoT, DNSCrypt, and Choosing a Resolver

Support for DNS-over-HTTPS, DNS-over-TLS, and DNSCrypt is the core of the resolver side. All three encrypt DNS queries in transit, and all three are supported alongside custom DNS servers. That combination — protocol choice plus server choice — is more flexibility than most Android DNS tools offer, and it is the main reason people seek this app out.

The flexibility is also the burden. Because you select the resolver, the privacy properties of your setup depend on that selection. A resolver that keeps detailed logs changes what your encrypted DNS actually buys you. The app encrypts the path; it does not vouch for the endpoint. Effectiveness depends on the blocklists and the resolver the user chooses, which the fact data lists plainly as a limitation rather than a footnote.

Encryption here applies to DNS traffic specifically. The app’s described behavior is that queries are handled locally or forwarded to your chosen resolver over an encrypted protocol. That is a narrower claim than “all your traffic is encrypted,” and the difference matters when you are deciding whether this replaces a VPN. It does not, on the evidence available.

Blocklists and Filtering: What Gets Blocked and What Does Not

Filtering is domain-based and driven by blocklists you enable. That means the app’s behavior is a direct function of your list choices. Enable nothing and nothing is filtered. Enable aggressive lists and you will block more, including things you may have wanted. The fact data offers no recommended list, no default configuration, and no guidance on which lists suit ads versus trackers, so any specific recommendation would be invention.

This is where the “blocks all ads everywhere” expectation breaks down. DNS filtering operates at the domain level, which is a different layer from in-page content blocking. The fact data makes no claim that DNS blocking replaces browser-based ad blocking, and treating it as a substitute will leave visible ads in place on many sites. The two approaches complement each other; they do not substitute for each other.

There is also a maintenance dimension nobody advertises. Blocklists change, domains rotate, and a list that works well this month can break a login flow next month. Because filtering effectiveness depends on the lists and resolver you chose, the app’s real-world quality is partly your responsibility. That is a fair trade for people who want control and a frustrating one for people who want a product that decides for them.

How to install

The official site is rethinkdns.com, and the app is distributed through Google Play and F-Droid. Those are the two channels the project’s own material lists. If you are going to install it, start from the official site and follow its links rather than hunting for an APK on a mirror, particularly given that the exact version number and release date are not published in the material available here.

F-Droid is a natural fit for this app because the code is open source under MPL-2.0, and F-Droid: An Open Source App Catalog for Android is one of the two listed distribution channels, which makes it a sensible entry point for anyone who prefers catalog-verified builds over store builds.

If you have moved away from Google Play, Aurora Store on Android: What It Does and Who It Suits covers the other common route to installing Android apps without the Play Store, which is worth reading before you decide how to get this one onto a device.

Two practical unknowns to keep in mind during installation: the APK size and the minimum Android version are not specified in the fact data. Neither is the current install count or user rating. That does not make the app suspect — it makes the listing incomplete, and it means you should check compatibility on your own device rather than trusting a summary.

Per-App Firewall Rules and Connection Logs

The firewall allows or blocks network access on a per-app basis, and the app keeps connection logs. That combination is the part that separates RethinkDNS from pure DNS filters. You can decide that one app gets no network access at all while everything else proceeds normally, and you can look at the log to see what has been happening.

The mechanism is Android’s VPNService, and that has a consequence worth stating plainly: only one app can hold the VPN slot at a time. This is why RethinkDNS may conflict with other VPN apps, and it is the direct answer to whether you can run it alongside WireGuard or another VPN. In practice you will be choosing one or looking for workarounds the fact data does not describe. The conflict is structural, not a bug.

Battery behavior in always-on mode is another unknown. No figures appear in the material available, and claims of zero impact should be treated skeptically for any app that inspects traffic continuously. The honest position is that always-on filtering has some cost and the size of that cost is not documented here.

On logging, the app maintains connection logs as a feature. Whether anything beyond those local logs leaves the device depends on diagnostics and telemetry settings, which the fact data does not describe as on or off by default. Read the official privacy policy before assuming your query history stays put.

RethinkDNS suits hands-on users: resolver choice, blocklists, and per-app rules

This is a tool for people who want to make decisions. If you are comfortable choosing a DNS protocol, picking a resolver, selecting blocklists, and writing per-app rules, the app gives you exactly the levers you would want. The learning curve is the price of the control, and the control is real.

It also suits people who care about inspectable software. The codebase is public at github.com/celzero/rethink-app and licensed under MPL-2.0, so anyone with the inclination can check what the app does rather than trusting a description. For a tool that sits in the network path, that matters more than it does for a calculator.

Privacy-focused users often assemble a small stack rather than relying on one app, and the same instinct that leads someone to a local DNS resolver tends to lead them to local secret storage — Aegis Authenticator on Android: What It Does and Who It Suits is the comparable case for two-factor codes, and reading it alongside this review gives a clearer picture of what a local-control toolkit looks like.

Who should skip RethinkDNS: users who want a one-tap ad blocker

If you want a one-tap ad blocker with no configuration, this is the wrong app. The filtering only works as well as the lists you enable, and the app does not present a single switch that handles everything. People who will not tune blocklists or rules will get less out of it than they expect.

Non-technical users should be warned off directly. DNS protocols, resolver selection, and per-app firewall rules are all decisions the app asks you to make, and the fact data lists configuration complexity as a genuine drawback rather than a hypothetical one. Handing this to someone who wants their phone to “just work” tends to produce a support conversation.

Anyone expecting a full VPN for anonymity or geo-unblocking is in the wrong category. This is a local resolver and firewall using the VPN slot, not a tunnel to a remote exit node. Likewise, anyone wanting antivirus-style malware protection should look elsewhere; filtering domains is not scanning for threats.

Finally, people who require guaranteed app support and zero breakage should think hard. Filtering depends on third-party lists and a resolver you chose, and misconfiguration can break logins or app functionality. Expecting zero battery impact from always-on filtering is also unrealistic given what the app is doing.

RethinkDNS vs AdGuard DNS and Pi-hole: Where Each Filtering Model Breaks

Blokada is the closest match on the ad-blocking side: it also uses a local VPN on Android to filter traffic, and it is generally pitched at users who want blocking without as much configuration. AdGuard for Android is the commercial option, with ad-blocking and filtering plus firewall-like features, and it comes with the support expectations that a paid product implies.

NetGuard is the closest direct alternative on the firewall side, because it also uses Android’s VPN slot to implement per-app network control without root, which makes NetGuard on Android: What It Does and Who It Suits the natural side-by-side read on firewall behavior and the trade-offs of occupying that slot.

The trade-off across all three comes down to scope. RethinkDNS bundles resolver, firewall, and blocklists in one app, which is convenient but means one configuration surface governs everything. Splitting the jobs across separate apps gives you clearer boundaries and more chances for two of them to fight over the VPN slot.

Licensing, Source Code, and Distribution

RethinkDNS is developed by Celzero and licensed under the Mozilla Public License 2.0. The source is hosted publicly at github.com/celzero/rethink-app, which is the claim behind the “open-source codebase that can be inspected publicly” advantage. For a security and privacy tool, that is not a marketing point; it is the difference between trusting a description and verifying one.

MPL-2.0 is a file-level copyleft license, which means the project’s openness is durable in a way that a permissive license would not guarantee. You do not have to care about license mechanics to benefit from them, but you should care that the license is stated clearly and that the repository is where the project says it is.

Distribution runs through Google Play and F-Droid, both listed as official channels. The app is free. What is not published in the material available here is the exact latest version, its release date, the APK size, the minimum Android version, or current install and rating figures. Those gaps are worth naming because they are the questions people ask first, and the honest answer is that this review cannot supply them.

Verdict

RethinkDNS is a legitimate, well-scoped privacy tool for a specific kind of Android user: someone who understands that DNS is a chokepoint, wants encrypted queries to a resolver of their choosing, and wants per-app network control without rooting the phone. The combination of a local resolver, a per-app firewall, and blocklist filtering in one open-source app is genuinely uncommon, and the MPL-2.0 license plus a public repository makes the whole thing checkable.

It is not for everyone, and the app’s own limitations say so. Configuration is complex, filtering is only as good as the lists and resolver you pick, and the VPNService dependency means it will collide with other VPN apps. Anyone who wants a one-tap blocker, a full anonymity VPN, antivirus protection, or a setup that never breaks should look at a different category of software entirely.

The unresolved questions are real and worth repeating: the interaction with Android Private DNS is not documented in the material available, battery behavior in always-on mode is unquantified, and whether diagnostics or telemetry are on by default is unstated. None of those are reasons to avoid the app. They are reasons to read the official privacy policy, test on your own device, and configure DNS in one place rather than assuming the layers sort themselves out. For the reader who wants control and is willing to spend an evening learning the interface, RethinkDNS earns its place. For everyone else, the honest advice is that this is more tool than they asked for.

Pros

  • Open-source codebase that can be inspected publicly
  • Combines DNS filtering and per-app firewall functions in one app
  • Supports encrypted DNS and user-selected resolvers

Cons

  • Uses Android VPNService, so it may conflict with other VPN apps
  • DNS and firewall configuration can be complex for non-technical users
  • Filtering effectiveness depends on the blocklists and resolver chosen by the user
Download from the official source

The link goes straight to Celzero. We do not host app files.

Open official page →

Frequently asked questions

Is RethinkDNS free?

The recorded pricing model is Free.

What license does it use?

It is listed under MPL-2.0.

Where can I download the official version?

The official link points to https://rethinkdns.com/app.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.