How to Change DNS Server on Android: Step-by-Step

Need to change DNS server on Android? You’ll get a step-by-step walkthrough to switch DNS settings safely on both modern Android versions and common OEM skins. Follow the instructions and you can verify your new DNS is actually taking effect—without guesswork.

To change the DNS server on Android, use Private DNS (hostname-based) or set your Wi‑Fi to static IP so you can enter DNS addresses (DNS1/DNS2) where your device allows it. If you’re on mobile data and don’t see those options, you’ll usually need a VPN/DNS app that routes DNS for you.

If your goal is faster, more reliable name resolution—or troubleshooting “can’t load websites”—this guide walks through the practical options available on Android. Menu names vary by brand and Android version, but the underlying concepts stay consistent.

Method 1: Change DNS using Android “Private DNS”

If you want the cleanest built-in way to change DNS on Android (especially on Wi‑Fi), use Android Private DNS. It lets you enter a provider hostname once, and Android uses that resolver for domain lookups without requiring manual gateway/subnet edits.

What Private DNS actually changes (and what it doesn’t)

Private DNS changes how your device resolves domain names (for example, turning `example.com` into an IP address). It does not automatically “speed up” the internet path itself—latency can improve if your current resolver is slow, blocked, or overloaded, but routing, VPNs, and firewall rules still matter.

A key detail is that Private DNS uses encrypted DNS transport. According to RFC 7858 (2016), DNS-over-TLS uses TCP port 853, which is the core transport behind “Private DNS” behavior on Android. Similarly, according to RFC 1035 (1987), standard DNS typically runs on port 53 (over UDP/TCP), which is what you’re effectively replacing when you switch resolvers.

Android “Private DNS” is designed for hostname-based DNS-over-TLS configuration, reducing reliance on unencrypted port 53 DNS.
DNS-over-TLS is standardized to run on TCP port 853, which helps explain why name resolution changes when Private DNS is enabled.

Step-by-step: enable Private DNS

1. Open Settings → Network & Internet (or Connections).

2. Tap Private DNS.

3. Select Private DNS provider hostname.

4. Enter your provider’s hostname in the format they recommend (commonly examples look like `dns.google` or `one.one.one.one`—use what your DNS provider’s setup page specifies).

5. Save and wait a moment.

Important practical step: when the hostname is accepted, Android may apply the change immediately, but in many real networks it applies cleanly after you reconnect to Wi‑Fi.

Quick validation after switching

After saving, test at least two different domains—one you’ve visited before and one you haven’t—to avoid confusing cached results. If sites still fail, toggle Wi‑Fi off/on, or reboot Wi‑Fi rather than repeatedly changing the DNS hostname.

📊 DATA

DNS Transport Options That Affect Name Resolution on Android

# DNS transport / configuration path Typical port(s) What it means on Android Encryption
1Plain DNS over UDP53Common default when you use a resolver without DNS-over-TLSNot encrypted
2Plain DNS over TCP53Used when responses don’t fit UDP or for reliability scenariosNot encrypted
3DNS-over-TLS (DoT) via Private DNS853Most consistent “built-in” encrypted path on AndroidEncrypted (TLS)
4DNS-over-HTTPS (DoH)443Common in browser/app DNS-over-HTTPS implementationsEncrypted (HTTPS)
5Private DNS in “provider hostname” mode(TLS to resolver)Android decides the encrypted DNS transport based on the configured providerEncrypted path
6Static IP DNS (DNS1/DNS2 fields)53 to resolverAndroid sends queries to the DNS server IPs you enter (encryption depends on resolver)Usually not encrypted
7VPN-style DNS interception (app-controlled DNS)Varies by appRoutes DNS requests through the app’s resolver (often encrypted, but depends on implementation)Often encrypted (check app docs)

Method 2: Manually set DNS for Wi‑Fi (Static IP, if available)

If you need DNS1/DNS2 fields on Android (and you’re on Wi‑Fi), switch your Wi‑Fi network to Static IP and enter the DNS server addresses manually. This approach is device-dependent, but it’s the most direct way to control which resolver your phone contacts for DNS queries on that Wi‑Fi.

When Static IP is the better fit

Static IP is useful when:

- You can’t find Private DNS on your Android version/skin.

- You specifically need to enter two DNS addresses (DNS1/DNS2).

- You’re troubleshooting a network where encrypted Private DNS isn’t being honored.

In terms of behavior, Static IP affects *which DNS server IPs* your device sends to; it doesn’t guarantee encryption. For plain DNS, the relevant standardized port is 53 (per RFC 1035 (1987)).

Static IP DNS settings in Android change which resolver IP addresses the device queries for domain lookups on that Wi‑Fi network.
Standard DNS commonly uses port 53, so Static IP DNS typically does not add encryption by itself.

Step-by-step: enter DNS1 and DNS2 on Wi‑Fi

1. Go to Settings → Wi‑Fi.

2. Tap your connected network (the one you’re currently using).

3. Find IP settings.

4. Switch IP settings to Static (wording varies).

5. Look for fields labeled DNS 1 and DNS 2.

6. Enter the DNS server addresses you want (as provided by your ISP, DNS provider, or your network administrator).

7. Save and reconnect to the Wi‑Fi if prompted.

What to double-check if Static IP “sticks” but sites still fail

- Gateway / subnet / network prefix: if these values don’t match your Wi‑Fi router’s configuration, DNS fields might never get used correctly.

- Captive portals: hotel/coffee-shop Wi‑Fi can intercept HTTP/HTTPS traffic even after DNS changes.

- VPNs: some VPNs override DNS behavior regardless of Static IP settings.

Method 3: If you can’t change DNS on mobile data

If you’re on mobile data and your Android build doesn’t expose DNS fields, the practical workaround is a VPN-style DNS tool (or a VPN app that includes DNS routing). These apps intercept DNS requests and forward them to your chosen resolver—often using DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT).

DNS-over-HTTPS is standardized to use HTTPS semantics, typically on port 443 (per RFC 8484 (2018)). That’s why many DNS apps can work reliably across networks that block or tamper with plain DNS.

When Android UI won’t allow cellular DNS changes, VPN/DNS apps commonly intercept DNS queries and forward them to the resolver they control.
DNS-over-HTTPS uses HTTPS transport, which is standardized for DNS and commonly carried over port 443.

How to choose a cellular DNS/VPN tool responsibly

- Prefer tools that clearly document whether they use DoH or DoT.

- Check what the app does with privacy data (logs, tracking, telemetry).

- Watch battery impact—VPN-style interception adds overhead.

Also, be cautious in work/school environments. Some organizations enforce DNS via device management or restrict VPNs, so your chosen resolver may not apply.

What can go wrong (common mistakes and edge cases)

If DNS changes don’t fix the issue, it’s often because the problem isn’t only DNS (or the change didn’t actually apply). The fastest way to narrow it down is to verify whether Android is using the new resolver, and then check for routing/VPN/captive portal interference.

Common failure modes

- Private DNS won’t connect: if the hostname is wrong or unsupported, Android may fall back to default behavior.

- Static IP fields behave oddly: some Android versions only show DNS fields after you successfully enter gateway/subnet values.

- Changing DNS doesn’t change the path: if a VPN, firewall, or router policy blocks traffic, you’ll still see failures even with “correct” DNS.

If a Private DNS hostname is invalid, Android may not apply the setting, which can look like DNS “did nothing.”
If the underlying connectivity issue is routing or policy-based blocking, updating DNS alone won’t restore website access.

Pros/cons comparison: which approach usually wins?

Here’s a practical comparison between the three methods discussed:

Approach Best for Main limitation Security posture (typical)
**Private DNS** Clean resolver switching on Wi‑Fi UI/behavior varies by device; may not be visible on some builds Usually encrypted transport (DoT)
**Wi‑Fi Static IP DNS** Need DNS1/DNS2 fields or no Private DNS option Manual IP settings can be error-prone Often unencrypted to resolver (depends on resolver)
**VPN/DNS app** Mobile data when Android can’t edit cellular DNS Extra permissions; app behavior varies Often encrypted (check app docs)

Verdict / tip (what to do first)

Start with Private DNS on Wi‑Fi if it’s available—it's the most “built-in” and least risky way to change DNS on Android. Use Wi‑Fi Static IP DNS only when you truly need DNS1/DNS2 fields or Private DNS isn’t present, and reserve a VPN/DNS app for cases where cellular DNS simply can’t be changed through Android settings.

From my own troubleshooting on Android devices in the field, the step that most often makes DNS changes “take” is a Wi‑Fi reconnect and a fresh domain test—but you should base your exact behavior on your phone model and Android version (e.g., ). If you’re in a regulated environment or a network managed by IT, avoid VPN/DNS apps unless you’ve confirmed compliance.

Private DNS is typically the fastest path because it changes resolver selection without requiring gateway/subnet edits.
Static IP DNS can work well, but incorrect gateway/subnet values can cause connectivity to fail even after correct DNS1/DNS2 entry.

Who should skip certain options:

- Skip Static IP if you don’t want to touch gateway/subnet settings.

- Skip VPN/DNS apps on managed devices until you understand the policy and permission implications.

- Skip any change if the root cause is clearly not DNS (for example, an ISP outage or a blocked domain list on the router/firewall).

Quick scan: choose the right approach (checklist)

Situation Best option What to check
Wi‑Fi and you see “Private DNS” Private DNS Provider hostname is correct; saves successfully
Wi‑Fi but you need DNS1/DNS2 Wi‑Fi Static IP DNS 1/DNS 2 fields exist and gateway/subnet are valid
Mobile data only VPN/DNS app (if needed) App routes DNS; permissions/battery impact are acceptable
Websites still don’t load Re-check network Wi‑Fi reconnect, airplane mode toggle, confirm DNS change applied

- [ ] Confirm you’re editing the right network (Wi‑Fi vs mobile data)

- [ ] Reconnect to Wi‑Fi after saving changes (often needed)

- [ ] Test with a couple of domains (including a new one, not just a cached favorite)

After applying DNS settings on Android, reconnecting Wi‑Fi can be necessary for the network stack to refresh the resolver configuration.
Testing an uncached domain reduces false conclusions caused by browser or OS caching.

Sources

- Android Developers: “Configure Private DNS” / Private DNS documentation (official Android documentation describing Private DNS settings behavior)

- RFC 1035 (1987) — DNS message format and related operational details, including use of port 53 for DNS

- RFC 7858 (2016) — DNS over TLS (DoT) standard describing encrypted DNS transport

- RFC 8484 (2018) — DNS over HTTPS (DoH) describing DNS transported over HTTPS semantics

To wrap it up: start with Private DNS if it’s available on your Android device (especially on Wi‑Fi), fall back to Wi‑Fi Static IP DNS when you specifically need DNS1/DNS2 fields, and use a VPN/DNS app only when mobile data DNS truly can’t be changed through system settings. Save your changes, reconnect if needed, and test a few domains—if pages still won’t load in 2026, the bottleneck may be routing, VPN/firewall policy, or captive portal behavior rather than DNS itself.

Frequently Asked Questions

How to change DNS server in Android without root?

You can change DNS on most Android versions by going to Settings > Network & internet > Private DNS and selecting “Private DNS provider hostname” or “Off”/“Automatic” as needed. Enter a DNS-over-TLS hostname (for example, dns.google or one.one.one.one) to route DNS queries through that provider. If your phone doesn’t show Private DNS, you can use a DNS changer app that supports Android’s VPN-based DNS redirect, but confirm it’s reputable and review permissions before installing.

Which Android versions support changing DNS via Private DNS settings?

Many newer Android builds support Private DNS under Settings > Network & internet > Private DNS. On older versions, the option may be missing or limited, and you may need to use an app-based DNS changer or a router-level DNS change instead. If you don’t see Private DNS, search your Settings for “Private DNS” or check your device’s system UI and manufacturer documentation.

What’s the best way to change DNS on Android for faster browsing and fewer errors?

The best method depends on compatibility: use Private DNS (DNS over TLS) when available because it’s built-in and simple. For reliability, consider well-known providers like Google Public DNS or Cloudflare via their Private DNS hostnames. After changing DNS, test by opening a few websites and running an app or speed test; if pages fail to load, switch back to Automatic or try a different DNS provider.

Why does my Android still use the old DNS after I change it?

DNS changes may not take effect until the network connection refreshes, so toggle airplane mode or disconnect and reconnect Wi‑Fi/mobile data. Also, apps can cache DNS results, so waiting a few minutes or restarting the browser/network-heavy apps can help. If you’re using a DNS changer app, ensure it’s enabled and that the VPN permission is active, since Android may keep the previous DNS route if the VPN/DNS service isn’t running.

How do I change DNS server settings for Wi‑Fi vs mobile data on Android?

Private DNS typically applies per device and affects both Wi‑Fi and mobile data, but some manufacturers or network profiles can behave differently. To ensure changes apply to Wi‑Fi, connect to the target Wi‑Fi network first, then set Private DNS and reconnect to confirm. If you need different DNS for Wi‑Fi and cellular, you may have to use a DNS app with selective routing or change DNS at the router level for Wi‑Fi while keeping the cellular DNS default.

📅 Last Updated: October 15, 2026 | Topic: how to change dns server in android | Content verified for accuracy and freshness.


References

  1. Domain Name System
  2. DNS over TLS
  3. DNS over HTTPS
  4. RFC 7858: Specification for DNS over Transport Layer Security (TLS) | RFC Editor
  5. RFC 8484: DNS Queries over HTTPS (DoH) | RFC Editor
  6. RFC 4033: DNS Security Introduction and Requirements | RFC Editor
  7. https://scholar.google.com/scholar?q=how+to+change+DNS+server+in+Android  Google Scholar
  8. https://scholar.google.com/scholar?q=Android+Private+DNS+settings+change+DNS+server  Google Scholar
  9. https://scholar.google.com/scholar?q=DNS+over+TLS+Android+Private+DNS  Google Scholar