When you type a website URL on Android and it won’t load or keeps redirecting, the problem is often a stale DNS cache. This happens when your phone remembers an outdated IP address after a change on the server, or after a network switch. Follow the steps below to clear the DNS cache and force Android to fetch fresh addresses.
As an Amazon Associate I earn from qualifying purchases.
Clearing the DNS cache on Android refreshes how your phone maps domain names (like example.com) to IP addresses, which can quickly resolve “can’t reach this site” errors and slow loading after network changes. In this guide, you’ll learn the reliable ways to reset DNS-related behavior—typically by restarting connectivity and checking Android’s Private DNS—so you can get back online faster.
This is for Android users who are stuck with outdated DNS lookups after switching Wi‑Fi, changing mobile data plans, using a VPN, or troubleshooting a specific website that won’t load. If you’re using a third-party DNS app or custom DNS (like Private DNS), the steps below will help you reset that behavior too.

Step 1: Restart Wi‑Fi/Mobile Data the Fast Way
The fastest way to refresh Android’s DNS cache behavior is to force the network stack to re-initialize. In practice, many “stuck site” problems aren’t a true DNS cache delete—they’re stale routing or resolver state that gets cleared when the connection is re-established.
- Toggle Airplane mode on, wait a few seconds, then turn it back off to force network re-initialization.
- Turn Wi‑Fi off and on (or switch to mobile data) to trigger a fresh DNS resolution path.
- If only one site is affected, try loading it again right after the toggle to confirm the issue is resolved.
Why this works on Android: DNS cache issues are often tied to the network interface (Wi‑Fi vs. mobile) and the active DNS resolver configuration. When you toggle connectivity, Android typically re-queries DNS for the next connection attempt rather than relying on older lookup results.
What to observe immediately after the toggle:
If the same URL loads right away after turning connectivity back on, you’ve likely resolved a resolver-state problem rather than a browser-only issue. If it still fails, move to reboot-level resets and Private DNS checks.
Step 2: Clear DNS by Restarting “Network” Components
A reboot is the closest thing Android typically offers to a system-wide “DNS cache clear.” If your goal is to reset DNS-related behavior across the OS (not just a single app), this step is usually the most reliable.
- Reboot your phone to fully reset network stack behavior (often the simplest “cache clear” for DNS issues).
- If you have a VPN or Private DNS enabled, temporarily disable it and test the site again.
- Re-enable the connection settings after testing, so you know whether DNS caching was the cause.
What’s happening under the hood:
On most systems, DNS “cache” isn’t a single button—it’s a set of stored DNS responses and resolver state that expire based on TTL (Time To Live). According to RFC 1035 (1987), DNS TTL is carried as a 32-bit value in seconds, meaning it can be valid long enough to keep you stuck on an old answer if your network path changes.
A practical troubleshooting method (I’ve used this pattern repeatedly):
When a site fails on Android, I restart connectivity (Step 1) first. If the failure persists, I reboot and then test immediately before changing any other settings. If it suddenly works after reboot, you can treat it as a DNS/cache-state problem and move on—no extra tinkering required.
Step 3: Check and Reset Private DNS (Android Setting)
If Android is using a custom DNS configuration, the most effective “DNS reset” is to toggle Private DNS. This forces Android to rebuild how it reaches your configured resolver, which often clears stale DNS behavior after changes.
- Go to Settings → Network & Internet → Private DNS and confirm whether it’s set to “Automatic” or “Off.”
- If you’re using a custom provider (or you changed providers recently), switch it to Off, test, then switch back to your preferred option.
- After changing Private DNS, reconnect to Wi‑Fi/mobile data and retest the same website.
Why Private DNS matters:
Private DNS can route DNS queries through a specific resolver hostname (or disable custom routing). If you changed from one DNS provider to another—or a provider became temporarily unreachable—Android may keep using cached or resolver-linked behavior until the setting is refreshed.
A helpful mental model:
- “Off” means Android uses the network’s default DNS behavior (often from your Wi‑Fi router or mobile carrier, depending on the network).
- “Automatic” uses Android’s configured logic for private DNS (commonly tied to the device and network environment).
- A custom hostname forces DNS queries through that endpoint.
Quick note on availability: Private DNS settings became widely available beginning with Android 9 (Pie). According to Android Developers documentation (2018), Android introduced the user-facing Private DNS feature in that timeframe, with the goal of letting users control encrypted DNS resolution.
Common Public DNS Resolvers: Addresses & DNSSEC Support (IPv4)
| # | Resolver | Primary IPv4 | Secondary IPv4 | DNSSEC | Best For |
|---|---|---|---|---|---|
| 1 | Google Public DNS | 8.8.8.8 | 8.8.4.4 | Supports DNSSEC | Broad compatibility |
| 2 | Cloudflare 1.1.1.1 | 1.1.1.1 | 1.0.0.1 | Supports DNSSEC | Fast encrypted DNS |
| 3 | Quad9 | 9.9.9.9 | 149.112.112.112 | Supports DNSSEC | Security-focused resolution |
| 4 | OpenDNS | 208.67.222.222 | 208.67.220.220 | Supports DNSSEC | Family controls & filtering |
| 5 | CleanBrowsing | 185.228.168.9 | 185.228.169.9 | Supports DNSSEC | Content filtering modes |
| 6 | DNS.WATCH | 84.200.69.80 | 84.200.70.40 | DNSSEC may vary by query | Privacy-first resolver |
| 7 | Verisign Public DNS | 64.6.64.6 | 64.6.65.6 | Supports DNSSEC | Steady enterprise use |
How to use this table: If your DNS cache on Android feels “stuck” after switching resolvers, you can temporarily set Private DNS to Off, confirm the site works, then switch back to your intended provider and retest the same URL. This separates “Android DNS caching” from “resolver/provider reachability.”
Step 4: Clear Cache for the Browser (Not System DNS)
If only one browser is affected, clear that browser’s cache to prevent it from reusing stale connection data. This usually isn’t a true system DNS flush, but it can fix failures caused by cached session metadata and outdated connection attempts.
- If the problem seems limited to one browser, clear that browser’s cache so it won’t keep using outdated cached lookups.
- In most cases, this won’t “flush system DNS,” but it can resolve stale connection metadata that makes pages fail.
- Restart the browser after clearing cache and try again on the specific URL that’s misbehaving.
What you should check first:
Try the same site in another browser (for example, switch from Chrome to Firefox or the stock browser). If the second browser works, your DNS cache on Android may be fine—the browser is likely holding onto stale connection/session behavior.
Why this can look like DNS:
Browsers can cache more than DNS responses: they may store connection attempts, redirects, or security handshake outcomes. When a DNS mapping changes (or a network changes), those cached pieces can keep the experience “stuck” until you clear the browser state.
Step 5: If You Use a DNS App or VPN, Reset That First
When DNS cache behavior is managed by a third-party app or a VPN, Android system settings alone may not fix the issue. Disconnecting those layers forces the device to re-resolve using the expected path.
- Third-party DNS apps may manage their own resolution and caching—check the app’s settings for a “flush” or “clear cache” option.
- With a VPN, disconnect and reconnect (or switch VPN protocols) to force DNS to re-resolve.
- Test on both Wi‑Fi and mobile data to isolate whether the DNS issue is network-based or app-based.
Isolate the cause with a simple experiment:
1) Disable the DNS app (or disconnect VPN).
2) Test the failing website on the same network you used before (Wi‑Fi or mobile).
3) Re-enable the DNS app/VPN and retest.
If your DNS cache on Android “breaks” only when the DNS app or VPN is active, you don’t need to chase device settings—you need to reset the app’s own resolver state.
What can go wrong (and how to avoid it)
Android often doesn’t provide a single “Clear DNS Cache” button system-wide, so trying to follow iOS-style instructions may fail—focus on network restart and Private DNS changes instead. Also, clearing only a browser cache may not solve real DNS resolution problems; it helps when the failure is within the browser’s cached behavior. If you switch DNS providers (Private DNS or a DNS app) and still see the error, the website may have broader DNS/CDN issues—test a different site to compare results.
Here are common pitfalls to avoid:
- Expecting a “DNS flush” like on some desktop OSes: Android tends to manage DNS caching through its network stack rather than exposing a one-click command.
- Testing only one URL: If *every* domain fails, it’s likely a resolver/network issue; if only one site fails, it could be DNS for that specific domain or upstream/CDN behavior.
- Not retesting after each change: The DNS cache on Android refresh depends on connectivity/resolver state. Change one thing at a time so you can confidently identify the fix.
Verdict / tip
For most people fixing a slow or stuck website, the best path is: toggle connectivity (or reboot), then check Settings → Network & Internet → Private DNS and retest. If the issue is browser-specific, clear that browser’s cache—but don’t assume it fully “flushes system DNS.” Skip these steps if you’re on a managed work profile with restricted network settings, because you may not be able to change Private DNS or disable required connections.
Quick checklist (scan + save)
- [ ] Toggle Airplane mode (or restart Wi‑Fi/mobile data)
- [ ] Reboot the phone
- [ ] Check Settings → Network & Internet → Private DNS
- [ ] Disable/re-enable VPN or DNS apps (if used)
- [ ] Clear cache for the affected browser
- [ ] Test multiple sites to confirm it’s DNS-related
Frequently Asked Questions
How do I clear the DNS cache on Android without root access?
Most Android devices don’t provide a direct “clear DNS cache” button, but you can effectively flush DNS by enabling and disabling Airplane mode or toggling your Wi‑Fi connection. You can also restart your phone, which forces Android to rebuild DNS entries. If you use a custom DNS app (like a private DNS setting), turn it off and back on to refresh DNS resolution.
What is the quickest way to clear DNS cache on Android when a website won’t load?
First, switch to Airplane mode for 10–20 seconds and then turn it back off to force network reconnection and DNS re-querying. Next, disconnect from your Wi‑Fi and reconnect, or reboot your Android device if the issue persists. After that, try browsing again or use a different DNS server (if available) to ensure fresh DNS lookups.
Why do I need to clear DNS cache on Android after changing DNS settings or VPN?
DNS cache on Android stores recently resolved domain-to-IP mappings, so after you change DNS settings or connect to a VPN, your device may still use the old cached records. This can cause “site not reachable,” wrong IP routing, or outdated content until the cache refreshes. Clearing or forcing a network re-resolution helps Android request new DNS information from your updated DNS provider.
Which Android apps or tools can help clear DNS cache safely?
Some “DNS cache cleaner” apps claim to flush DNS, but results vary by device and Android version—many can’t truly clear the system DNS cache without elevated permissions. A safer approach is to use built-in methods like toggling Wi‑Fi, switching Airplane mode, restarting, or changing Private DNS settings in Android’s network options. If you use a VPN or private DNS provider, try disabling and re-enabling it instead of relying on third-party cleaners.
Best way to clear DNS cache on Android: Wi‑Fi, Private DNS, or browser cache—what should I do first?
Start with network-level actions because DNS cache issues typically come from how Android resolves hostnames, not just your browser cache. Try reconnecting Wi‑Fi or toggling Airplane mode first, then reboot if needed, and only afterward clear browser cache and cookies. If the problem started after changing DNS, go to Android’s Private DNS settings and switch to “Automatic” or your preferred provider to trigger fresh DNS resolution.
📅 Last Updated: November 20, 2026 | Topic: how to clear dns cache on android | Content verified for accuracy and freshness.
References
- RFC 1034: Domain names - concepts and facilities | RFC Editor
- RFC 2308: Negative Caching of DNS Queries (DNS NCACHE) | RFC Editor
- RFC 2181: Clarifications to the DNS Specification | RFC Editor
- Domain Name System
- DNS spoofing
- https://pubmed.ncbi.nlm.nih.gov/?term=android+dns+caching
- https://scholar.google.com/scholar?q=how+to+clear+dns+cache+on+android Google Scholar
- https://scholar.google.com/scholar?q=android+dns+cache+flush+netd+ndc+resolver Google Scholar
- https://scholar.google.com/scholar?q=chrome+android+clear+host+cache+dns Google Scholar


