Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


To remove a Private DNS hostname on Android, open Settings > Network & internet > Private DNS, choose Automatic (or Off for a short test), and tap Save; the phone then stops using that custom provider. To change Private DNS on Android to another provider, record the current mode, choose Private DNS provider hostname, and enter only a hostname supplied by a DNS provider or administrator you trust. Test both Wi-Fi and mobile data before treating either change as complete.
Key Takeaways
- Android uses Private DNS by default on networks that support it, and Google recommends leaving it enabled.[1]
- The custom field expects a provider hostname, not a regular DNS server IP address.
- Private DNS protects DNS questions and answers; it does not encrypt every connection, change your public IP, or replace a VPN.
- A captive portal, wrong hostname, filtered network, or managed policy can make a correct-looking setting fail.
- Save the original mode and restore it after a temporary diagnostic test.
Start with the device and app troubleshooting guide if you have not yet shown that DNS is the failing layer. A Wi-Fi icon, a browser error, and a broken app can point to different problems.
Private DNS is Android's system setting for encrypted DNS on compatible networks. It protects the questions your device sends to a DNS resolver and the answers it receives. Google explicitly limits that protection to DNS traffic.
It does not prove that a website is trustworthy, encrypt an app that uses an insecure connection, hide your public IP address, or repair a router or mobile carrier outage. The broader DNS guide explains how resolver selection differs from the rest of a network connection.
Android presents three modes:
| Mode | What it means | When to use it |
|---|---|---|
| Off | Do not request Android Private DNS | A short, controlled diagnostic or a network that cannot support it |
| Automatic | Use Private DNS when the current network supports it | The safest normal default for most users |
| Private DNS provider hostname | Connect to one named provider | Only with an exact, trusted hostname |
Menu names can vary by manufacturer and Android version. Google advises searching Settings for “Private DNS” or asking the device manufacturer when the option is not in the expected location. Pixel's current advanced-network guide also notes that steps can vary by device.[2] Do not install an unrelated app or configuration profile merely to make the menu appear.
Create a small recovery record before touching the setting:
Do not store passwords, internal hostnames, or organization details in a public ticket. If the field is locked, a value returns after you change it, or the hostname belongs to an organization, stop and contact its administrator. A device policy, security product, or work profile may own the setting.
If every device fails on the same Wi-Fi, use the Android Wi-Fi no-internet checklist before changing one phone. If only mobile data fails, use the Android mobile data guide.
Use the system setting rather than a third-party shortcut:
These are Google's current Android steps, but the manufacturer may rename or relocate them. A custom hostname is not the same field as a numeric DNS address shown in Wi-Fi IP settings. Do not paste an IP address, a web URL, a username, or a search result into the hostname field.
Change one variable at a time. Do not simultaneously forget the Wi-Fi network, reset mobile settings, disable a proxy, and change Private DNS; that would make the result impossible to attribute.
Verification should show that ordinary use still works on each network type you rely on:
Do not use a marketing “DNS leak” page as the only proof. A web page can show one resolver observation, but it cannot prove that every app, work profile, local network name, or captive portal behaves correctly.
If the change fixes only one network, document that network dependency. If it breaks both Wi-Fi and mobile data, first recheck the hostname for transcription errors and confirm that the provider still supplies that hostname.
Hotel, airport, school, and guest networks may require a sign-in page before normal internet access is allowed. A custom resolver can be unreachable before that authorization or can conflict with the network's local naming and filtering design.
For a network you are authorized to use:
Use Off only when Automatic does not isolate the problem and you understand the temporary loss of encrypted DNS. Do not leave protection disabled merely because one captive portal was poorly designed. Never bypass an organization policy or certificate warning to force access.
Local printers, NAS names, parental controls, and split DNS can also depend on a resolver chosen by the network or organization. If a custom hostname breaks only those destinations, ask the network owner how local names are intended to resolve instead of adding random exceptions.
To stop using a custom hostname you no longer want:
Switching the mode is the removal step; you do not need to reset network settings or install another app. If the hostname comes back or the option is grayed out, treat it as a managed value and follow the support steps below.
To undo a test instead, return to the same screen and select the mode from your recovery record. If it was custom, enter the exact original hostname, save, and repeat the same Wi-Fi and mobile-data checks.
If the setting will not save, immediately reports a connection failure, or keeps returning to a managed value, preserve the error and stop changing adjacent settings. Give support the phone model, Android version, network type, chosen mode, hostname owner, and the comparisons you ran. Do not send private account details or organization credentials.
Android uses Private DNS by default on networks that support it. The normal Automatic mode lets the device use it when available.
Enter only the exact hostname published by a resolver provider or administrator you trust. Do not enter an ordinary IP address, webpage URL, or search result.
No. It changes how compatible DNS queries are handled; it does not replace the network address assigned by your carrier, router, or internet provider.
No. Private DNS protects DNS questions and answers. A VPN is a separate network layer that can carry broader traffic through a tunnel.
The hostname may be wrong, the provider may be unavailable, the current network may block the connection, or a captive portal may not be complete. Restore Automatic and compare networks before changing anything else.
Try Automatic first, complete the authorized captive portal, and then restore your original mode. Use Off only as a brief diagnostic when you understand the tradeoff.
A managed device or network policy may control network settings. If a value is locked or returns automatically, contact the administrator rather than trying to remove the policy.
No. It cannot repair weak Wi-Fi, an expired mobile plan, a failed router, an app outage, a wrong proxy, or a blocked account. Scope the symptom before using it as a fix. Android Private DNS configures resolver transport; a VPN carries traffic through a tunnel, so neither one repairs a broken router or an unavailable app account.
Sources:
Sources checked 4 October 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





