Quad9 Is Leaving France: What to Change on Your Devices
Quad9 stops serving users in France on 24 November after a Paris court sided with beIN. We explain what to change on routers, phones, browsers and VPNs.
Primary source: quad9.net
Quad9, a free DNS resolver that turns website names into the numeric addresses devices need, will stop serving users in France on Tuesday 24 November 2026. The Swiss nonprofit announced the move on 22 October, the day after a Paris court ruled for the broadcaster beIN in a sports piracy case.
On 17 November, Mullvad published advice for users of its browser in France, who it says are affected. Anyone in France who set Quad9 by hand on a router, phone or browser has a week to change it.
What happened
On 13 May, a Paris court ordered Quad9 to block IPTV sites, which stream TV channels over the internet, for users in France. The court found that the sites infringed beIN Sports France’s rights to the WTA tennis tour. The block ran until the season’s last match, on 14 November.
Quad9 told the court it had blocked none of the sites’ domain names. On 21 October 2026, the Paris Judicial Court ordered it to comply or pay €1,000 for each day of delay. Quad9 says the court cut the penalty from €580,000 a day.
Quad9’s response
Quad9 says it cannot obey the ruling and stay true to its mission. It keeps no list of users by country, so it cannot reliably tell who is in France. It could add the names to the malware blocklist behind its main 9.9.9.9 service, but that would apply a French ruling to users everywhere.
Blocking by location has failed it before. In a German case, Quad9 blocked content only for users in Germany, but Sony Music reached it through a VPN and the court fined Quad9. So Quad9 will leave France instead, while its appeal against the May order goes on.
Mullvad’s advice
Mullvad is involved because of a change it announced in September. It said it would close its own public encrypted DNS service on 2 November, fund Quad9 instead and move Mullvad Browser users on the default setting there. Its new post gives those users in France three options:
- Switch the browser’s DNS over HTTPS provider, which receives its lookups in encrypted form, from Quad9 to Cloudflare or another service.
- Turn DNS over HTTPS off, which Mullvad recommends when you use a VPN, and accept that your lookups then go to your French internet provider.
- Use Mullvad VPN.
People outside France are not affected, Mullvad says. With its VPN connected, the VPN server you use resolves DNS inside the encrypted tunnel.
Why it matters
For Quad9’s users in France, the change removes a layer of protection. Its main service blocks known malware and phishing domains. Quad9 says it sees French traffic from government agencies, universities, hospitals and utilities, as well as home and mobile users.
Mullvad says Quad9 will refuse DNS requests from France, so a router, phone or browser still set to use it will be turned away. The order in this case ended with the tennis season, which caps the penalty at €24,000 by Quad9’s count. Quad9 is leaving anyway, because it says about 20 other pending cases in France could bring penalties it “cannot survive”.
Where a VPN fits in
A VPN changes what happens on the device that runs it. Most VPN apps send lookups through the encrypted tunnel to a resolver the provider runs, as our guide to how a VPN works explains. Every VPN we review says it uses its own resolvers. Quad9’s guides add that Android’s Private DNS setting is not used while a VPN is on, and that most VPN apps ignore its iPhone profile.
What to do
Quad9’s addresses start with 9.9.9 or 149.112.112, or with 2620:fe in the newer IPv6 format, and its encrypted service uses names ending in quad9.net. Check each place it could be set before 24 November:
- Router or computer. Replace those addresses with another resolver, or set DNS back to automatic so your internet provider answers.
- Android phone. Search Settings for Private DNS. If it shows dns.quad9.net, enter another provider or switch it off.
- iPhone, iPad or Mac. Remove any Quad9 DNS profile you installed.
- Browser. In Mullvad Browser, go to Settings, then Privacy and security, and open Advanced settings under DNS over HTTPS. Pick Cloudflare or another provider, or turn it off if you use a VPN.
- VPN app. If you entered Quad9 as custom DNS, as Quad9’s guides suggest, switch back to the default. Then run our VPN check to confirm your traffic leaves through the VPN.
Turning encrypted DNS off without a VPN is the quickest fix, but your internet provider then sees each site you look up. Our page on whether a VPN is worth it explains what that reveals. Another public resolver may not be a lasting answer either, because Quad9 says the pending French cases also target other resolver operators.
What we changed
Our Mullvad review now covers Mullvad’s switch to Quad9 for its browser and links to this report. We also added a note on browser DNS settings to our guide to how a VPN works. No prices, features or scores change, because Quad9 is not a VPN and Mullvad’s VPN app resolves DNS on its own servers.
Pages updated because of this
Frequently asked questions
When does Quad9 stop working in France?
Why is Quad9 leaving France?
Do I need to change anything if I use a VPN?
How do I change the DNS setting in Mullvad Browser?
Sources
- 1. Quad9 blog: Farewell, France (22 October 2026) (accessed 17 Nov 2026)
- 2. Tribunal judiciaire de Paris, judgment of 21 October 2026, beIN Sports France v. Fondation Quad9, RG 26/11882 (published by Quad9) (accessed 17 Nov 2026)
- 3. Mullvad blog: Quad9 will withdraw their DNS service from France (17 November 2026) (accessed 17 Nov 2026)
- 4. Mullvad blog: Shutting down our public encrypted DNS servers and sponsoring Quad9 instead (3 September 2026) (accessed 17 Nov 2026)
- 5. Mullvad help: Install Mullvad Browser, How to change the DNS from Quad9 (accessed 17 Nov 2026)
- 6. Quad9: Service addresses and features (accessed 17 Nov 2026)
- 7. Quad9 documentation: Android 9 and later (encrypted) (accessed 17 Nov 2026)
- 8. Quad9 documentation: iOS 14 and later (encrypted) (accessed 17 Nov 2026)
Changelog
- First published.