Mac Captive Portal Not Showing? Check Your DNS

If your Mac joins a Wi-Fi network but the captive portal login page never appears, check your DNS settings before you waste time restarting the connection or blaming the network.

I ran into this at a Capital One Lounge. My Mac connected to the Wi-Fi, but the login page never opened. Another laptop on the same network worked fine, so the problem was clearly local to this machine.

The culprit turned out to be custom DNS.

What was happening

I had recently configured Cloudflare DNS on my Wi-Fi connection:

1.1.1.1
1.0.0.1

Those DNS servers are usually great. But captive portal networks, like lounges, hotels, cafes, airports, and airplanes, often expect your device to use the DNS server they provide.

When your Mac joins a Wi-Fi network, DHCP typically hands it three important things:

an IP address
a default router
a DNS server

On a captive portal network, that DNS server may intentionally redirect certain requests so macOS can detect that the network requires a login page.

Because I had hard-coded Cloudflare DNS, my Mac ignored the network-provided DNS server. The result was simple: the captive portal never appeared.

The fix

Reset Wi-Fi DNS back to automatic so macOS can use the DNS server the network provides.

From Terminal:

networksetup -setdnsservers Wi-Fi Empty

Or in macOS:

System Settings -> Wi-Fi -> Details -> DNS

Then remove the custom DNS entries.

After that, disconnect and reconnect to the Wi-Fi. Once the network's DNS was being used again, the captive portal showed up immediately.

Why this happens

Captive portals are a little hacky by design. They often rely on DNS interception and HTTP redirects to push your device toward a login or acceptance page.

That setup works only if your device is actually using the network's DNS resolver.

If you override DNS with Cloudflare, Google, Quad9, or anything else, you can break the captive portal flow without realizing it.

Short version

If your Mac connects to hotel, airport, cafe, airplane, or lounge Wi-Fi but the login page never opens, check whether you have custom DNS configured.

If you do, remove it and let DHCP provide the network's DNS server.

That is often the difference between "Wi-Fi is broken" and "the portal opens instantly."