↔P2Priv 8 entries · updated 2026-11-01

Mullvad’s public DNS is closing: check your settings before November 2

Who needs to act before Mullvad’s public encrypted DNS shutdown, how to switch to Quad9, and why DNS privacy does not hide your IP from peers.

P2Priv Editorial Team · 4 min read

If you manually configured Mullvad’s public encrypted DNS, switch before November 2, 2026. Mullvad is closing that public service and financially supporting Quad9 instead. This is not a shutdown of Mullvad VPN’s internal DNS. The immediate privacy concern is your domain lookups—not the IP address another peer sees. Mullvad’s announcement sets the migration deadline.

Who needs to act?

Mullvad’s migration instructions distinguish these configurations:

Your setup What to do
Mullvad VPN using its normal internal DNS No public-DNS migration is needed for that setup. Check separately configured browsers or devices.
Mullvad Browser with default DoH or its included ad-blocking option Mullvad says these will migrate automatically to Quad9. Keep the browser updated and verify afterward.
Mullvad Browser with a manually selected Mullvad DoH variant Change it back to the default. Customized DoH settings will not be changed automatically.
Another browser, Android Private DNS, router or resolver manually using Mullvad’s public service Replace the Mullvad configuration before the deadline.
An existing Mullvad iOS or macOS DoH profile Replace it with a Quad9 profile; Mullvad says existing profiles will stop working.

Search your settings for dns.mullvad.net and variants such as adblock.dns.mullvad.net, base.dns.mullvad.net, extended.dns.mullvad.net, family.dns.mullvad.net and all.dns.mullvad.net. Mullvad’s public-service documentation lists both DNS over HTTPS (DoH) and DNS over TLS (DoT) configurations, including their IP addresses. Check either type, not just browser settings; some resolvers may have the addresses configured separately from the hostname.

How to replace the public resolver

Quad9’s recommended service provides malicious-domain blocking and DNSSEC validation, without the optional EDNS Client Subnet feature.

  • Browser or other DoH client: replace the old custom endpoint with https://dns.quad9.net/dns-query.
  • Android 9 or later: search Settings for Private DNS, select Private DNS provider hostname, enter dns.quad9.net, then save. Use a hostname here, not the DoH URL or an IP address. See Quad9’s Android instructions.
  • iPhone, iPad or Mac: remove the old Mullvad DNS profile and follow Quad9’s iOS 14 and later or macOS Big Sur and later profile guide. Download through Safari and choose the recommended HTTPS (.9) profile. As of October 28, 2026, the guides list January 19, 2027 as the profiles’ expiry date; they automatically disable at expiry, so set a renewal reminder.
  • Windows 11: follow Quad9’s encrypted-DNS guide. It uses 9.9.9.9 and 149.112.112.112 with DNS over HTTPS enabled; configure IPv6 too if your connection uses it. Leave Fallback to plaintext off if encryption is required, accepting that lookups may fail on networks that block DoH.

Changing a DNS IP address alone does not enable encryption. Retain an explicit DoH or DoT configuration if you want encrypted lookups outside a VPN. For routers and DNS forwarders, also check compatibility: Quad9 no longer supports HTTP/1.1 for DoH, so an older client may need updating or a supported DoT configuration.

Do not assume equivalent filtering. Mullvad offered ad, tracker, adult-content and other blocking variants; Quad9 says it focuses on malicious domains and does not provide general content filtering. A successful DNS migration does not necessarily preserve your previous blocking policy.

Verify the resolver—and the encryption

Open Quad9’s resolver check in the browser you changed. A “Yes” confirms that check used Quad9; it does not prove every application uses it or that DNS was encrypted.

For a system or router configuration, Quad9 documents a separate protocol test. On Windows PowerShell, run:

Resolve-DnsName -Type txt proto.on.quad9.net.

On systems with dig:

dig +short txt proto.on.quad9.net.

The reply doh or dot identifies encrypted transport received by Quad9. do53-udp or do53-tcp identifies ordinary DNS transport. This tests the connection reaching Quad9, not necessarily the whole path from your device. For example, a router can receive ordinary DNS from a device and forward it to Quad9 over DoH.

These commands do not test browser-only DoH. Quad9 also warns that dig and nslookup do not use Apple’s encrypted-DNS profiles, so do not use their results to judge an iOS or macOS profile. VPNs and iCloud Private Relay can override system DNS settings. If you need to disconnect a VPN to check your non-VPN configuration, close peer-to-peer applications and other traffic you do not want outside the tunnel first.

What this changes for peer-to-peer privacy

DoH and DoT protect DNS queries between the DNS client and the resolver. The resolver still receives those queries; encryption does not remove that trust relationship. The DoH specification explicitly discusses server-side correlation, including the client IP address.

DNS encryption does not relay your peer traffic or replace its source IP. BitTorrent’s protocol specification describes peer connections separately, with tracker responses supplying peer addresses and ports. Switching from Mullvad DNS to Quad9 therefore does not hide your address from a directly connected peer. See what other peers can see for that boundary.

If you already use Mullvad VPN’s normal DNS, leave that configuration alone unless you have a separate reason to change it. Mullvad says the public encrypted service is primarily for use outside its VPN; inside the tunnel, it adds negligible security benefit and is slower than the VPN-server resolver.