DnsOverHttpsMode = off). Let the network signal Firefox to turn off its automatic DoH, and answer "no such domain" for iCloud Private Relay (DNSAFE does this when SafeSearch enforcement, a Kids profile or Secure Wi-Fi is on). Then decide your VPN policy.1. Hard-coded DNS servers
Some devices and apps ignore the DNS servers your network hands out and use their own, such as 8.8.8.8 or 1.1.1.1. The fix is a firewall rule:
- Allow outbound UDP and TCP port 53 only from your DNS servers (the firewall itself or your domain controllers) to the DNSAFE addresses.
- Block outbound port 53 from every other internal address.
- Also block outbound TCP 853 (DNS-over-TLS) except to the DNSAFE resolver IPs (all three regions:
3.12.124.91,3.11.62.44,52.220.82.194). Android Private DNS uses this port, so the rule covers it too.
Some firewalls can instead redirect stray port-53 traffic to your DNS server (often called DNS interception or a port-forward NAT rule). That's friendlier than blocking, because the device still gets filtered answers.
2. Browsers' own encrypted DNS (DoH)
DNS-over-HTTPS sends lookups inside normal HTTPS traffic on port 443, so a port rule can't catch it. Handle it at the browser:
Chrome and Edge
Chrome only upgrades to DoH automatically when the system's DNS provider supports it, but users can pick their own provider in settings. On managed computers, set the DnsOverHttpsMode policy to off:
- Group Policy: Computer Configuration → Administrative Templates → Google → Google Chrome → Controls the mode of DNS-over-HTTPS → Enabled → Disable DNS-over-HTTPS. Edge has the same policy under Microsoft Edge.
- Registry:
HKLM\SOFTWARE\Policies\Google\Chrome, string valueDnsOverHttpsMode=off. - Intune or Google Admin console: the same setting is in their Chrome policy lists.
Firefox
Firefox checks a "canary" domain, use-application-dns.net. If the network's DNS says it doesn't exist, Firefox leaves its automatic DoH off. DNSAFE answers that way for every registered network, so this works without extra setup. It doesn't override a user who switched DoH on themselves, so on managed computers also set Firefox's DNSOverHTTPS policy to disabled and locked.
Known DoH providers
For extra coverage, block the hostnames of public DoH services at the DNS layer. When SafeSearch enforcement, a Kids profile or Secure Wi-Fi is on, DNSAFE blocks well-known DoH endpoints automatically.
If you want encrypted DNS that still filters, point devices at DNSAFE's own DoH address instead. Step by step in the docs: DNS-over-HTTPS setup.
3. iCloud Private Relay
On iPhones, iPads and Macs with iCloud+, Private Relay covers Safari, all DNS lookups on the device, and unencrypted HTTP traffic from apps, sending them through Apple's relays. Apple's guidance for networks that need filtering is to make mask.icloud.com and mask-h2.icloud.com fail to resolve (no answer, or "no such domain"). The device then tells the user that Private Relay is off for this network. Avoid silently dropping the traffic, which causes slow timeouts.
DNSAFE does this when SafeSearch enforcement, a Kids profile or Secure Wi-Fi is on. You can also add both names to your block list.
4. VPNs and proxies
A VPN app sends all traffic, including DNS, to its own servers. DNS filtering can't see inside it. Your options:
- Policy: an acceptable-use policy that forbids personal VPNs on company devices, enforced with device management.
- Block the VPN services' domains: add popular consumer VPN sites to your block list so they can't be downloaded or signed in to. This helps, but it's not airtight.
- Next-generation firewall: application control can recognize and block most VPN protocols.
For devices that leave the network: per-device encrypted DNS (Roaming devices) keeps your policy anywhere, or Secure Wi-Fi carries all traffic through an encrypted tunnel with your policy on.
5. Your internet provider's IPv6 DNS
When your internet provider also gives the network IPv6, the router or firewall can hand devices the provider's IPv6 DNS server alongside yours (in router advertisements or DHCPv6). Phones and computers may use it, and those lookups skip DNSAFE. The protection test shows this as Partly protected, with your provider's DNS next to DNSAFE.
- Turn IPv6 off on the router or firewall your devices connect to. Browsing and apps keep working over IPv4. Home router steps: TP-Link, NETGEAR, ASUS, eero, Google Nest Wifi, Linksys, Verizon Fios.
- Or keep IPv6 and stop advertising the provider's DNS: on business firewalls, set the IPv6 DNS the LAN hands out (RDNSS / DHCPv6 DNS) to none, or to your internal DNS server that forwards to DNSAFE.
- Or protect devices directly with per-device encrypted DNS (Roaming devices on Business, DNS IDs on Home). They send every lookup to DNSAFE whatever the network hands out.
Try DNSAFE on your own network: 14 days free, no card, set up in minutes.
Start free trialCheck your work
- From a test device, run
nslookup example.com 8.8.8.8. With the port-53 rule in place it should time out or be refused. - Open Chrome's
chrome://policyand confirmDnsOverHttpsModeshowsoff. - Run the DNS leak test in each browser. Every one should show DNSAFE.
Frequently asked questions
Is DNS-over-HTTPS bad for businesses?
No, encryption is good. It becomes a problem when a browser sends lookups to a provider you didn't choose. The fix is to use encrypted DNS to your own filtering provider (DNSAFE supports DoH and DoT) and turn off the browser's own choice.
Will blocking iCloud Private Relay break iPhones?
No. Following Apple's guidance, the device shows a notice that Private Relay isn't available on this network and carries on without it. Everything else works normally.
Can I stop every possible bypass?
Not with DNS alone. A determined user with admin rights can install a VPN. The steps above close the common routes; device management and a firewall with application control close most of the rest.