Your iPhone quietly caches DNS responses in the background to speed up browsing, but that same cache can become a source of real frustration when you're hitting old IP addresses, landing on the wrong version of a website, or getting mysterious connection errors after a domain migration. Unlike Windows or macOS, iOS does not give you a single terminal command to flush DNS. Instead, there are several methods depending on what you actually need to clear, and knowing which one to use will save you time and repeated reboots that accomplish nothing.

Why DNS Cache Problems Happen on iPhone

Every time your iPhone resolves a domain name, the operating system stores the result temporarily so it doesn't have to query a DNS server on every single request. This is standard behavior and it works well under normal conditions. The problem surfaces in a handful of specific scenarios:

  • Domain migration or hosting change — You or your team pointed a domain to a new server. The old IP is cached on the device and iOS keeps using it even though DNS propagation is complete everywhere else.
  • TTL (Time-To-Live) was set too high — If the previous DNS record had a TTL of 86400 seconds (24 hours), iOS may hold onto that value for the full duration regardless of what has changed upstream.
  • Captive portal or hotel Wi-Fi conflicts — Some networks inject DNS responses that get cached and cause issues after you switch to a different network.
  • ISP resolver poisoning or staleness — Your carrier's recursive resolver gave your phone a stale answer, and your device cached it faithfully.
  • App-level DNS caching — Safari, Chrome, and third-party apps each maintain their own connection and session caches on top of the OS-level DNS cache.

Method 1: Toggle Airplane Mode On and Off

This is the fastest method and works for most everyday DNS cache issues. Enabling Airplane Mode tears down all active network connections, which forces iOS to release cached DNS entries associated with those interfaces. When you disable Airplane Mode, the device rebuilds its network stack fresh.

  1. Open Settings and tap Airplane Mode to turn it on. The toggle turns green and all radios shut down.
  2. Wait a full 30 seconds. A quick toggle is not enough time for all cached state to clear.
  3. Tap Airplane Mode again to turn it off.
  4. Wait for Wi-Fi or cellular to reconnect fully, then retest the site or app.

This method clears the in-memory DNS cache but does not clear app-level caches in Safari or Chrome. If the problem is browser-specific, proceed to Method 3 or 4 after this step.

Method 2: Reboot Your iPhone

A full reboot is more thorough than Airplane Mode. It clears all in-memory state including DNS cache, socket connections, and network interface configurations. Many engineers recommend this as a default first step precisely because iOS handles so much transparently in the background.

  1. iPhone X and later (Face ID models): Press and hold the Side button and either Volume button simultaneously until the power slider appears. Drag the slider, wait 30 seconds, then press the Side button to power on.
  2. iPhone SE (2nd/3rd gen), iPhone 8 and earlier (Touch ID models): Press and hold the Top or Side button until the slider appears. Drag to power off, wait 30 seconds, then restart.

After the reboot, reconnect to your network and test. For most propagation-related DNS issues, this combined with clearing browser cache is all you need.

Method 3: Clear Safari Cache on iPhone

Safari maintains its own DNS and connection cache separate from the OS. If a domain change is showing correctly on other browsers or devices but not in Safari, this is the culprit.

  1. Open Settings and scroll down to Safari.
  2. Scroll down and tap Clear History and Website Data.
  3. Tap Clear History and Data in the confirmation dialog.
  4. Return to Safari and reload the affected page with a hard refresh by tapping and holding the reload icon, then selecting Reload Without Content Blockers if available, or simply reloading.

Note that this action removes your browsing history and logged-in sessions, so be aware if you have active logins you haven't saved passwords for.

Method 4: Clear Chrome Cache on iPhone

Chrome on iOS caches DNS independently from Safari and the iOS system cache. If you primarily use Chrome, follow these steps:

  1. Open Chrome and tap the three-dot menu in the bottom right.
  2. Tap Settings, then Privacy and Security, then Clear Browsing Data.
  3. Select Cached Images and Files and Cookies, Site Data. Set the time range to All Time.
  4. Tap Clear Browsing Data and confirm.

Chrome also has an internal DNS resolver page accessible in the desktop version but not on iOS, so clearing cache via settings is the only option on iPhone.

Method 5: Change Your DNS Server

If you're consistently getting stale or incorrect DNS responses, switching to a faster, more reliable public DNS resolver will bypass your ISP's resolver entirely. This is especially useful if your carrier's DNS is known to cache aggressively or return incorrect results.

  1. Open Settings and tap Wi-Fi.
  2. Tap the information icon (i) next to your connected network.
  3. Scroll down to Configure DNS and tap it.
  4. Change the setting from Automatic to Manual.
  5. Delete the existing DNS servers by tapping the red minus button next to each entry.
  6. Tap Add Server and enter one of the following:
  • Cloudflare: 1.1.1.1 and 1.0.0.1
  • Google Public DNS: 8.8.8.8 and 8.8.4.4
  • Quad9 (security-focused): 9.9.9.9 and 149.112.112.112

Tap Save in the top right. This change only applies to the current Wi-Fi network. You'll need to repeat it for other networks, or consider using a DNS-over-HTTPS profile for system-wide coverage (discussed below).

💡 After flushing DNS and switching resolvers, verify that your domain is resolving to the correct IP worldwide using the DNS Propagation Checker. This lets you confirm whether the problem was local to your device or still propagating across global resolvers.

Method 6: Install a DNS-over-HTTPS Configuration Profile

iOS 14 and later support encrypted DNS (DoH and DoT) via configuration profiles. Installing one from Cloudflare or another provider sets a system-wide DNS resolver that applies to all apps, not just Safari, and forces cache refresh on all interfaces. This is the closest iOS gets to a true flush with a persistent improvement.

Cloudflare provides a free profile at 1.1.1.1.cloudflare-dns.com — visit that URL in Safari on your iPhone and follow the prompts to download and install the profile under Settings > General > VPN & Device Management. Once installed, go to Settings > General > VPN & Device Management > DNS and enable it.

This does not replace your VPN and does not route your traffic through Cloudflare's servers — it only sends DNS queries to their resolver over an encrypted channel.

Method 7: Forget and Rejoin the Wi-Fi Network

If you're on a network that pushed bad DNS settings (common with captive portals in hotels, airports, or corporate networks), forgetting the network clears the DHCP lease and all associated DNS settings including any cached resolver addresses assigned by that network's DHCP server.

  1. Open Settings > Wi-Fi and tap the info icon (i) next to the network.
  2. Tap Forget This Network and confirm.
  3. Reconnect to the network by selecting it from the list and entering the password.

How to Verify Your DNS Cache is Now Correct

After applying any of the above methods, you need to confirm the device is now resolving correctly — not just assume it is. There are two practical ways to do this from an iPhone:

Using a DNS Lookup App

Download a free app like Network Analyzer or DNS Lookup from the App Store. Enter the domain in question and run a lookup. The A record result should match the IP address your hosting provider or DNS zone shows as current.

Using a Web-Based DNS Lookup Tool

Open Safari on your iPhone and use the DNS Lookup tool on this site. Enter the domain, select the A record type, and compare the result against what your registrar or DNS host shows. If they match, your device is resolving correctly.

When DNS Flush Alone Won't Fix the Problem

If you've gone through every method above and still see wrong results, the issue is upstream from your device. Check these possibilities:

  • Your home router is caching DNS — Many consumer routers run their own DNS resolver (dnsmasq) and cache answers. Even if your iPhone flushes its local cache, it queries the router, which returns a stale cached answer. Log into your router admin panel and either flush its DNS cache or restart it.
  • Your ISP's resolver is stale — Some ISPs override TTL values and cache records longer than specified. Switching to a public resolver (Method 5) bypasses this completely.
  • The DNS change hasn't propagated yet — If the record was updated less than the TTL value ago, even authoritative propagation may not be complete. Check propagation status using the tool linked above.
  • The wrong DNS server is set at the domain level — Verify your domain's nameservers at the registrar level are pointing to the correct DNS host before troubleshooting further.

Router-Specific DNS Cache Flush Steps

If your iPhone is on Wi-Fi and you suspect the router is serving stale DNS, here are the admin interfaces for common home router brands:

  • TP-Link: Visit tplinkwifi.net or 192.168.0.1. Go to Advanced > Network > DHCP Server and look for a DNS Cache option, or simply reboot the router from the System Tools menu.
  • Netgear: Visit routerlogin.net or 192.168.1.1. Netgear consumer routers don't expose a DNS flush button — a router reboot is required.
  • Asus: Visit asusrouter.com or 192.168.1.1. Go to Administration > Reboot to clear the DNS cache, or use the Adaptive QoS section to configure custom DNS servers.
  • Linksys: Visit 192.168.1.1. Use the Administration > Management page to perform a router reboot.
  • D-Link: Visit 192.168.0.1. Navigate to Tools > System and use the Reboot option.

How to Prevent Repeated DNS Cache Issues on iPhone

Once you've solved the immediate problem, a few small changes will reduce how often you hit this situation again:

  • Use a public DNS resolver permanently — Set Cloudflare or Google DNS on your home Wi-Fi (Method 5) so you're not dependent on your ISP's resolver quality.
  • Lower TTL before DNS changes — If you manage DNS for your own domain, set the TTL to 300 seconds (5 minutes) at least 24-48 hours before any planned migration. This shortens how long any device — including iPhones — will cache the old record.
  • Use a DoH profile on your iPhone — The Cloudflare profile in Method 6 gives you encrypted, consistent DNS resolution across all networks including cellular and unknown Wi-Fi.
  • Reboot your router periodically — A monthly router reboot clears accumulated DNS cache entries and often improves overall network performance.

Summary of All Methods

  1. Airplane Mode toggle — 30-second fix, clears in-memory OS DNS cache.
  2. Full reboot — Most thorough OS-level flush, clears all network state.
  3. Clear Safari cache — Required if issue is Safari-specific.
  4. Clear Chrome cache — Required if issue is Chrome-specific.
  5. Change DNS server — Bypasses stale ISP resolver, per Wi-Fi network.
  6. Install DoH profile — System-wide resolver upgrade, persistent across all networks.
  7. Forget and rejoin network — Clears DHCP-assigned DNS settings from captive portals.

Work through these in order for the fastest resolution. In the vast majority of cases, the combination of a reboot and clearing Safari or Chrome cache resolves the issue within minutes. The DNS server change and DoH profile are worth doing regardless — they'll make every DNS resolution on your iPhone faster and more reliable going forward.