Outcome: You’ll enable Android Private DNS so your DNS lookups are encrypted instead of visible to your ISP on many networks.

Who this is for: Android users who want a quick privacy upgrade without installing a VPN or extra app.

Time required: About 2 minutes.

Quick Answer

Open Settings, search Private DNS, choose Private DNS provider hostname, and enter dns.google or one.one.one.one. Save, then verify browsing still works.

What this trick does

When Private DNS is enabled, Android sends DNS requests over encrypted DNS (DNS-over-TLS) to your chosen provider. That helps reduce plain-text DNS visibility on the network path and can improve privacy on public Wi‑Fi.

Prerequisites

  • Android 9 (Pie) or newer
  • Working internet connection for setup
  • A valid Private DNS hostname (for example, Google or Cloudflare)

Step-by-step: enable Private DNS on Android

  1. Open the Private DNS setting.
    Go to Settings > Network & internet > Private DNS (path may vary by device). You can also use Settings search and type Private DNS.
    Expected result: You see options like Off/Automatic/Private DNS provider hostname.
  2. Select provider hostname mode.
    Choose Private DNS provider hostname and enter one of these:
    dns.google (Google Public DNS)
    one.one.one.one (Cloudflare)
    Tap Save.
    Expected result: Internet remains connected and DNS queries use encrypted transport when supported.
  3. Test normal browsing.
    Open a few websites and apps you use daily.
    Expected result: Pages load normally with no “can’t connect” errors.
  4. Optional validation check.
    Open 1.1.1.1/help to inspect your DNS status and network details.
    Expected result: DNS provider details reflect your chosen resolver/network behavior.

Expected result checks

  • Setting check: Private DNS is set to Private DNS provider hostname.
  • Connectivity check: Websites and apps resolve domains without delay or failures.
  • Privacy check: DNS resolution is no longer sent in plain text where Private DNS is active.

Common mistakes

  • Typing an invalid hostname (a typo breaks DNS resolution).
  • Using an IP address instead of a provider hostname in this field.
  • Assuming Private DNS hides everything (it protects DNS lookups, not all traffic metadata).

Troubleshooting

  • No internet after saving: Reopen Private DNS and switch to Automatic, then retry with a correct hostname.
  • Can’t find the setting: Use Settings search; on Samsung it’s often under Connections > More connection settings > Private DNS.
  • Network blocks custom DNS: Some school/work/hotel networks may restrict it. Temporarily use Automatic on those networks.
  • Still worried about privacy: Pair this with HTTPS browsing and strong browser privacy settings.

References

Next step

After enabling Private DNS, test one public Wi‑Fi session this week and confirm everything works—then keep it on as your default privacy baseline.

Related reads