This Network Is Blocking Encrypted DNS Traffic: iPhone Fix Guide
Why your iPhone says this network is blocking encrypted DNS traffic, what the network can see, how to check if your DNS is encrypted, and the fix per router.
In this guide
iOS shows “This network is blocking encrypted DNS traffic” when the Wi-Fi network blocks DNS over HTTPS or DNS over TLS, so your iPhone cannot keep its name lookups private there. Browsing still works, but the names of sites you visit can be read on that network. Fix it on your own router; elsewhere, use a tunnel or another network.
Test it now
Cloudflare edgeRead at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.
Show detailsWhat the warning actually means
Encrypted DNS wraps your device’s name lookups in TLS so that nobody between you and the resolver can read or alter them. The two standard forms are DNS over TLS (DoT) on TCP port 853 (RFC 7858) and DNS over HTTPS (DoH), which hides queries inside ordinary HTTPS on port 443 (RFC 8484). Apple added system-wide support for both in 2020 with iOS 14 and macOS Big Sur, and said then what happens when a network interferes: some networks “block using your encrypted DNS server by policy,” usually because they “are trying to filter traffic by looking at DNS queries,” and when iOS detects this “a Wi-Fi network is marked with a privacy warning.” Apps configured for encrypted DNS then fail to connect rather than fall back to plain DNS.
The warning is a label on the network, not on your phone. Settings > Wi-Fi shows “Privacy Warning” under the network’s name, and the detail screen adds that the names of the websites and servers your device reaches may be visible to others on that network: without encryption, every lookup travels as readable text, even when the page itself uses HTTPS.
Apple has not published how the check works: asked on the Apple Developer Forums, an Apple DTS engineer said the detection algorithm is not documented and that another app on the device using encrypted DNS can be what triggers it. Read the warning as iOS reporting a failed attempt to use encrypted DNS on this network, nothing more precise.
Why is my iPhone displaying the “This network is blocking encrypted DNS traffic” warning?
The usual cause is a device on the network that answers or redirects DNS for everything connected to it. Each of these is documented by its vendor.
A Pi-hole or similar DNS filter. Pi-hole’s configuration reference lists dns.specialDomains.iCloudPrivateRelay, which defaults to true and makes Pi-hole “always reply with NXDOMAIN to A and AAAA queries of mask.icloud.com and mask-h2.icloud.com to disable Apple’s iCloud Private Relay to prevent Apple devices from bypassing Pi-hole.” Those are exactly the hostnames Apple tells network operators to return NXDOMAIN for when they want to block Private Relay, after which the user is alerted to disable Private Relay on that network or choose another one.
A gateway that redirects DNS. Ubiquiti’s documentation for UniFi Ad Blocking states that “clients using custom DNS servers are redirected to use the UniFi Gateway DNS server when Ad Blocking is enabled,” and lists encrypted DNS (DoH/DoT) and Apple iCloud Private Relay / Limit IP Address Tracking among the client features it cannot coexist with.
A subscription filter on a mesh system. eero’s support page for custom DNS says that “eero Plus works by filtering DNS requests from devices” and that custom DNS settings are grayed out while it is on.
A provider, campus or office network that filters DNS by policy. Apple’s Private Relay guidance acknowledges that “some enterprise or school networks might be required to audit all network traffic by policy” and can block the service; forcing plain DNS is how the filter gets to see it.
A captive portal you have not completed. Apple grants captive-network detection an automatic exception, but a portal intercepts traffic until you accept its page. Finish the login, then look again.
Is it dangerous? What plain DNS exposes and what HTTPS still hides
Plain DNS leaks metadata, not content. RFC 7858 describes the problem it was written to solve: nearly all DNS queries are sent unencrypted, which makes them vulnerable to eavesdropping and on-path tampering. Encrypting the page does not change that, because the lookup for the hostname happens before the HTTPS connection exists.
| What an observer on the network sees | Plain DNS (port 53) | Encrypted DNS (DoT 853 / DoH 443) |
|---|---|---|
| The hostnames you look up | Yes, in clear text | No |
| Whether an answer can be rewritten in transit | Yes, silently | No; tampering breaks the TLS session |
| The page content you load over HTTPS | No | No |
| The IP addresses you connect to afterward | Yes | Yes |
So the warning does not mean someone is reading your messages or passwords; HTTPS still protects those. Nor is encrypted DNS anonymity: destination IP addresses still cross the network in the clear, and the resolver you send encrypted queries to sees every name you ask for. The practical risk on an untrusted network is the hostname list, which is enough to profile what you use.
How do I know if my DNS is encrypted? Check it now
Run the check from the device that shows the warning, while it is on that network.
- Open the DNS server check. The page asks your resolver for a unique hostname that exists only on CheckMyIP’s own nameserver, so whichever resolver forwards that query is the one your device really uses. You get the resolver’s IP address, its operator (your ISP, a public service such as Cloudflare, Google or Quad9, or your own address if a Pi-hole answers), its country, and an “Encrypted DNS (DoH / DoT)” line that reports encrypted DNS when it can be detected from the resolver that answered; whether the last hop from your phone was encrypted depends on your settings.
- Compare the result with what you expect. If you installed a Cloudflare or Quad9 profile but the resolver shown belongs to your ISP or your router, the encrypted configuration is not in use on this network.
- For a longer sample, run the DNS leak test with the “No VPN” option. It sends six (or thirty-six) unique lookups and lists every resolver that handled them; a filter that intercepts only part of your traffic shows up as a second resolver. The guide to what a DNS leak is explains how to read that list.
- To test for the Private Relay block, look up
mask.icloud.comwith the DNS lookup tool (it runs from CheckMyIP’s servers, so it shows what the name should return), then runnslookup mask.icloud.comon a Mac or Windows PC on the same Wi-Fi. A public answer in the first place and “NXDOMAIN” or “can’t find” in the second means the network returns the block Apple describes.
Nothing from these checks is stored; CheckMyIP computes results in memory and discards them within ten minutes.
Fix it on your own router
The goal is a network that lets encrypted DNS pass and does not blackhole the Private Relay names. If you run a Pi-hole to block ads for the whole house, letting iPhones bypass it defeats the purpose; accept the warning or turn off Private Relay per network on those iPhones. If the filtering is a side effect you never asked for, turn it off.
Pi-hole (v6)
- On the Pi-hole host, run
sudo pihole-FTL --config dns.specialDomains.iCloudPrivateRelay false. Pi-hole’s configuration reference documents this--config key.name valueform; the same key can be edited in/etc/pihole/pihole.tomlor through the web interface. - Pi-hole then stops answering NXDOMAIN for
mask.icloud.comandmask-h2.icloud.com. Itsdns.specialDomains.mozillaCanaryoption (default true) does the same touse-application-dns.net, the canary Firefox checks before enabling DoH; set it to false the same way if you want browser DoH on the LAN. - On the iPhone, forget the Wi-Fi network and rejoin it.
UniFi gateways
Ubiquiti documents that Ad Blocking redirects any client with custom DNS to the gateway’s resolver and places the feature in the Application Firewall section of the Network application. Turn Ad Blocking off there, then forget and rejoin the Wi-Fi on the phone. Keeping it means living with the warning.
eero
eero documents two paths in its app. To stop the subscription filter from answering DNS: Home > Security & privacy > Network Controls, then turn off Advanced Security and Ad Blocking and remove any active content filters. To set your own resolvers afterward: Settings > Advanced networking > DNS, enable Custom DNS, enter the addresses and tap Save; the network reboots.
ISP gateways and other routers
Look in the gateway’s LAN or security pages for anything named DNS filter, DNS redirection, safe browsing, parental controls or DNS protection and turn it off, then set the WAN DNS servers you want. TP-Link’s FAQ for this warning on Deco systems is a typical vendor recipe: set the DNS servers manually in the Deco app (More > Internet Connection > IPv4), then forget the Deco network on the iPhone and reconnect. Re-run the resolver check after each change.
How do I enable encrypted DNS on the iPhone itself?
iOS has no field for typing a DoH or DoT server; Settings > Wi-Fi > ⓘ > Configure DNS > Manual, which Cloudflare and Google document, sets plain DNS addresses for that one Wi-Fi network only. Unlike Android, which has a system-wide Private DNS hostname field, iOS gets encrypted DNS in one of three ways.
- A DNS configuration profile from your resolver provider. Quad9’s guide for iOS 14 and later says to download the profile in Safari on the iPhone (other browsers will not work), open Settings > Profile Downloaded, select the Quad9 profile, tap Install, enter your passcode and tap Install again. Installed profiles are listed under Settings > General > VPN & Device Management. Profiles carry an expiry date: Quad9’s page is headed “Profiles expire on January 19th, 2027” and says an expired profile disables itself until a new one is installed, so plan to download a fresh one before then.
- An app that configures encrypted DNS. Apple’s NEDNSSettingsManager API lets a resolver’s app set the system DNS. Cloudflare’s 1.1.1.1 app, which its documentation calls the recommended way to set up 1.1.1.1 on iOS, installs a VPN profile when you enable it and can encrypt DNS queries.
- iCloud Private Relay. Part of an iCloud+ subscription and not available in every country, Private Relay encrypts your DNS records so that neither relay can see the website’s address and keeps your IP address from the sites you visit. You can switch it off for a single network with Settings > Wi-Fi > ⓘ > Limit IP Address Tracking.
None of these can force a way through a network that blocks the resolver; they give iOS something to use where the network permits it. Which resolver to point them at is a separate decision, covered in which DNS server you should use. After installing one, forget the network and rejoin: Settings > Wi-Fi > ⓘ > Forget This Network for the connected network, or Settings > Wi-Fi > Edit > ⓘ for any saved one.
When it is not your network: public, hotel or work Wi-Fi
On a network you do not control, nothing in Settings makes the warning go away, because the block is upstream. You can accept it, route around it, or leave.
- Accepting it is reasonable for a short session on sites you do not mind being seen; HTTPS still protects what you send and receive.
- Routing around it means tunneling DNS inside something the network does allow: iCloud Private Relay, if mask.icloud.com is not blocked, or any VPN, which carries DNS with the rest of your traffic. A VPN shifts trust to its operator rather than removing it.
- Leaving means cellular data or a personal hotspot, which bypasses the venue’s filter.
Work and school networks are a separate case: Apple’s guidance recognizes that some must audit all traffic by policy and may block encrypted services deliberately. On a managed device, the DNS Settings payload can be switched off on specific networks with on-demand rules, which Apple’s deployment guide describes; the warning then reflects policy, and the administrator is the person to ask.
Same warning on iPad and Mac
Apple’s WWDC20 description covers its platforms generally, and iPadOS shows the same label under the network name in Settings > Wi-Fi; the checks and fixes above apply unchanged on an iPad. A Mac uses the same encrypted-DNS configurations (profiles, apps, Private Relay), so the same block affects it. To forget a network on a Mac: Apple menu > System Settings > Wi-Fi, click Advanced, click the More Options button next to the network, choose Remove From List and click Forget. To turn Private Relay off for one network on a Mac: System Settings > Network > your service > Details > turn off Limit IP address tracking.
Apple’s pages for these steps were checked against the versions published on June 17, 2026 (screenshots from iOS 26 and macOS Tahoe 26) and October 1, 2026; the iPhone Settings paths come from the iOS 27 iPhone User Guide.
Confirm the fix: re-run the DNS check
After changing the router or installing a profile, forget and rejoin the Wi-Fi, then open the DNS server check again from the iPhone. Three things should line up: the resolver shown is the one you intended, the “Encrypted DNS” line agrees with your setup, and the Privacy Warning label is gone from Settings > Wi-Fi. If a different resolver still answers, something else on the path is intercepting port 53, and the DNS leak test will show whether it takes all of your lookups or only some.
Sources
- Apple WWDC20 session 10047, “Enable encrypted DNS” (transcript)
- Apple Developer Forums thread 661116, “DNS encryption blocked” (replies from Apple DTS engineering)
- Apple Developer: Prepare your network or web server for iCloud Private Relay
- Apple Support: About iCloud Private Relay
- Apple Support: Manage iCloud Private Relay for specific websites, networks, or system settings
- Apple Support: Forget a Wi-Fi network or prevent your device from automatically joining it
- iPhone User Guide (iOS 27): Manage Wi-Fi settings on iPhone
- iPhone User Guide (iOS 27): Install or remove configuration profiles on iPhone
- Apple Platform Deployment: DNS settings declarative configuration for Apple devices
- RFC 8484, DNS Queries over HTTPS (DoH)
- RFC 7858, Specification for DNS over Transport Layer Security (TLS)
- Pi-hole documentation: Configuration (pihole.toml, dns.specialDomains)
- Ubiquiti Help Center: UniFi Gateway - Ad Blocking
- eero Support: How do I set up custom DNS servers with eero?
- TP-Link FAQ 2943: The Weak Security and Privacy Warning on the iOS14 or iOS15
- Cloudflare 1.1.1.1 docs: Set up 1.1.1.1 on iOS
- Quad9 documentation: iOS 14 and later (Encrypted)
- Google Public DNS: Get Started (configure your network settings)
Questions
How do I remove DNS blocking?
On your own router, turn off the setting that redirects or filters DNS, or allow the Private Relay hostnames mask.icloud.com and mask-h2.icloud.com in your DNS filter. On a network you do not control you cannot remove it; use iCloud Private Relay, a VPN, or cellular data instead, and forget the network afterward.
How do I tell if my DNS is hijacked?
Open https://checkmyip.com/my-dns-server from the device. It shows the resolver that really answered a lookup against CheckMyIP’s own test zone. If you configured one resolver (for example 1.1.1.1 or your Pi-hole) and a different one appears, something on the path is intercepting port 53 and answering in its place.
Is DNS safer than a VPN?
They protect different things. Encrypted DNS hides only your name lookups from the local network and your provider; sites you visit still see your IP address. A VPN moves all traffic, including DNS, into a tunnel to the VPN operator, who then sees it instead. Use encrypted DNS everywhere and a VPN when you also need to hide your address.
Back to your own address: my IP address

