Outcome: You will encrypt Android DNS lookups so your ISP can’t easily read which domains you visit.
Who this is for: Android users (Android 9+) who want a fast privacy upgrade without installing a VPN app.
Time required: About 2 minutes.
Quick Answer
Open Settings > Network & Internet > Private DNS, choose Private DNS provider hostname, enter dns.google or one.one.one.one, then save and test at dnsleaktest.com. If the provider appears instead of your ISP, the trick worked.
Most people think they need a paid VPN to hide every browsing detail from their ISP. But one Android setting gives you meaningful privacy in under two minutes: Private DNS.
What this one trick does
Private DNS encrypts your DNS requests (the “site lookups” your phone does before connecting). That means your ISP has a harder time seeing domain-level activity from plain DNS queries, especially on public Wi-Fi.
On Android, this uses encrypted DNS (DNS-over-TLS) at the system level for supported networks.
Prerequisites
- Android 9 (Pie) or newer
- A working internet connection during setup
- A valid provider hostname (example:
dns.googleorone.one.one.one)
Step-by-step: Enable Private DNS on Android
- Open Private DNS settings.
Go to Settings > Network & Internet > Private DNS. On some phones (like Samsung), it may be under Connections > More connection settings.
Expected result: You should see options such as Off/Automatic/Private DNS provider hostname. - Choose a provider hostname.
Tap Private DNS provider hostname. Enterdns.google(Google Public DNS) orone.one.one.one(Cloudflare). Tap Save.
Expected result: Your phone reconnects, and internet access returns normally. - Verify it worked.
Open a browser and run an extended test at dnsleaktest.com.
Expected result: DNS servers should match your chosen provider, not your ISP’s default DNS.
Expected result checks
- Websites open normally after saving the hostname
- DNS leak test shows provider-owned resolvers (Google/Cloudflare) instead of ISP DNS
- No extra app required and setting stays active system-wide
Common mistakes
- Typing a full URL instead of just the hostname (use
dns.google, nothttps://dns.google) - Using an invalid hostname, which can break connectivity until corrected
- Skipping verification and assuming it works without testing
- Expecting total anonymity—Private DNS improves DNS privacy, but it is not a full VPN replacement
Quick troubleshooting
- No internet after saving: Re-open Private DNS and correct hostname typo, or switch to Automatic to confirm network compatibility.
- Still seeing ISP servers in test: Toggle airplane mode for 10 seconds, reconnect Wi-Fi/mobile data, then retest.
- Network blocks encrypted DNS: Some captive portals or enterprise networks may block strict private DNS; use Automatic temporarily.
- Pages feel slower: Try the other provider hostname and compare.
Official references
- Google Android Help: Private DNS settings
- Android Developers: Configure Private DNS
- Cloudflare setup: 1.1.1.1 on Android
Related reads
- Privacy in 3 Steps: Enable Private DNS on Android to Hide Browsing from ISP
- Hidden Android Feature: Notification History to Rescue Dismissed Alerts
- No-App Android Trick: Live Captions for Every Video and Call
Next step CTA: After enabling Private DNS, turn on Android’s built-in Private Wi-Fi MAC and review app network permissions for an extra privacy boost.