Outcome: You’ll encrypt your Android DNS lookups so your ISP can’t easily view the domains you request.

Who this is for: Android users on Android 9+ who want a fast, no-app privacy upgrade.

Time required: About 2 minutes.

Quick Answer

On Android, open Settings > Network & Internet > Private DNS, pick Private DNS provider hostname, enter dns.google or one.one.one.one, save, then verify with dnsleaktest.com.

Here’s one tiny setting with a big privacy payoff: Private DNS. It encrypts DNS requests, which helps prevent easy DNS-level tracking by your ISP or insecure networks.

Prerequisites

  • Android 9 (Pie) or newer
  • Internet connection for setup and testing
  • A valid private DNS hostname

Step-by-step: Enable Android Private DNS

  1. Open Private DNS settings.
    Go to Settings > Network & Internet > Private DNS (or search “Private DNS” in Settings).
    Expected result: You see Off, Automatic, and Private DNS provider hostname options.
  2. Set a provider hostname.
    Tap Private DNS provider hostname and enter one:
    – dns.google
    – one.one.one.one
    Tap Save.
    Expected result: Connectivity stays active after saving.
  3. Verify the switch.
    Open dnsleaktest.com and run Extended Test.
    Expected result: Resolver results show your selected provider instead of ISP default DNS.

Expected result checks

  • Web pages load normally after enabling Private DNS
  • DNS leak test shows provider-owned resolvers
  • No extra app required; setting works system-wide

Common mistakes

  • Entering a URL (https://dns.google) instead of hostname only
  • Hostname typo that breaks connectivity
  • Skipping leak-test verification
  • Assuming Private DNS is identical to a full VPN

Quick troubleshooting

  • No internet after save: Correct hostname spelling or switch to Automatic.
  • Still seeing ISP DNS: Toggle Airplane mode, reconnect, and retest.
  • Work/school Wi-Fi issue: Some managed networks block strict private DNS; use Automatic on that network.
  • Slow feel: Switch between Google and Cloudflare hostnames and compare.

Reference links

Related posts

Next-step CTA: After this, enable randomized/private Wi-Fi MAC and review app network permissions for a stronger mobile privacy baseline.