Android 'Connected, no internet'? It's Your Private DNS

That little exclamation mark next to your Wi-Fi icon is infuriating. You're connected. The password worked. And yet nothing loads. Nine times out of ten on Android 9 and up, this is Private DNS pointing at a hostname your current network can't resolve — a setting you probably enabled months ago and forgot about.

The fastest fix: turn Private DNS off. Here's how.

Fix #1: Private DNS set to a hostname that won't resolve

Open Settings → Network & internet → Private DNS. If it's set to Private DNS provider hostname and you see something like dns.google or one.one.one.one, that's your problem. Switch it to Automatic.

Reconnect to Wi-Fi. The exclamation mark should clear within 10-15 seconds. If it does, you've found the culprit.

Why does this happen? Private DNS forces Android to use DNS-over-TLS. That's great on a home network or mobile data. But on captive portals (hotel Wi-Fi, airport, coffee shops), corporate networks, or any ISP that hijacks DNS on port 853, the encrypted query gets blocked. Android can reach the router but can't resolve a single hostname — so it reports "connected, no internet."

A quick test to confirm: open Chrome and try to load https://1.1.1.1. If that works but google.com doesn't, DNS is the issue, not the connection.

If you want to keep Private DNS on for security (fair — I do too), set it back to Automatic when you're on the problem network and flip it to dns.google when you're home. Annoying, I know. Or use 1dot1dot1dot1.cloudflare-dns.com — it's slightly more permissive with captive portals in my experience.

Common trigger: You set up Private DNS at home, then walked into a hotel or a client's office where the network blocks port 853. The setting stays, the connection dies.

Fix #2: The Wi-Fi access point itself has no working upstream

Before you blame the phone, check another device on the same Wi-Fi. If your laptop also shows no internet, the problem isn't Android — it's the router.

Power-cycle the router. Unplug it, wait 30 seconds, plug it back in. I know it sounds like tier-1 boilerplate, but a surprising number of "Android DNS problems" are actually a router that lost its DHCP lease from the ISP and hasn't renegotiated. The router broadcasts Wi-Fi fine; it just has no WAN.

If a reboot doesn't fix it, log into the router admin (usually 192.168.1.1 or 192.168.0.1) and check the WAN status page. Look for a valid IP — anything starting with 169.254.x.x means the router failed to get a lease and is self-assigning. Call your ISP.

Fix #3: Stale DHCP lease or corrupt network state on the phone

If other devices on the same Wi-Fi work fine and Private DNS is already set to Automatic, the phone's network stack is probably holding onto bad state. Two things to try, in order:

1. Forget and rejoin the network. Settings → Network & internet → Internet → tap the gear next to your Wi-Fi name → Forget. Then reconnect. This wipes the saved IP, gateway, and DNS entries and forces a fresh DHCP handshake.
2. Reset network settings. Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. This nukes every saved network, VPN profile, and Bluetooth pairing on the phone — so only do it if step 1 fails. You'll need to re-enter every Wi-Fi password.

One more thing worth checking: if you've got a VPN app installed (NordVPN, Proton VPN, corporate clients like Cisco AnyConnect), and it crashed or got force-stopped while connected, it can leave a broken VPN tunnel that blocks all traffic. Open the app, disconnect, then uninstall it briefly to test. The Wi-Fi will come back immediately if that was it.

Quick reference

Start with Private DNS. It's the fix that solves the most cases and takes fifteen seconds.