A free security service is preparing to disappear from France—not because it failed to protect users, but because its operator refuses to turn it into a copyright filter. The Quad9 France DNS blocking dispute reaches beyond unauthorized sports streams: it asks whether a privacy-focused part of the internet’s infrastructure should decide which lawful requests for domain names receive an answer. Quad9, the Swiss nonprofit behind the 9.9.9.9 public resolver, says it will withdraw service from France beginning November 24, 2026, rather than implement a French court’s piracy-blocking order.
The immediate case concerns 58 domains allegedly used to distribute unauthorized tennis broadcasts. The larger issue is whether public DNS resolvers should become copyright enforcement intermediaries—and what that would mean for DNS neutrality, privacy, security and the open internet.
What happened in the beIN Sports copyright case?
Broadcaster beIN Sports asked a Paris court to require several public DNS providers to block domains associated with unauthorized tennis streams. The court ruled that Quad9 must prevent access through its resolver to a list of 58 domains. It also imposed a penalty of €1,000 for each day of non-compliance.
The ruling did not find that Quad9 hosted, published or transmitted the streams. Instead, it treated the resolver as an intermediary capable of contributing to piracy website blocking by refusing to resolve the listed domain names. This distinction is central to the controversy.
Quad9’s official statement says the nonprofit will stop offering its free cyberprotection service to users in France from November 24. As of November 18, that withdrawal is scheduled rather than completed. TorrentFreak’s reporting brought broader attention to the order, the 58-domain list and the financial penalty.
Three positions should not be conflated:
- The court’s finding: Quad9 can be ordered to participate in blocking under the applicable French copyright framework.
- Quad9’s position: geographically targeted filtering is incompatible with the design and privacy model of its global, free resolver, leaving withdrawal as the least harmful option.
- Cloudflare’s industry argument: DNS blocking is easy to bypass, risks overblocking and places enforcement duties on infrastructure that does not control the disputed content.
How recursive DNS works—and what Quad9 actually does
DNS is often described as the internet’s phone book. When someone enters a domain name, a recursive DNS resolver searches the DNS hierarchy and returns the corresponding IP address. The browser can then contact the server associated with that address.
Quad9 operates public DNS resolvers, including the well-known Quad9 9.9.9.9 service. Its security-focused resolver also checks requested domains against threat intelligence and can block domains linked to malware, phishing and other technical threats. Quad9 says it does not sell personal data and is designed to minimize collection of information that could identify users.
A recursive resolver is not the website’s hosting provider. It does not possess the allegedly infringing video, administer the destination server or control the domain registration. A hosting company can remove content from infrastructure it operates. A DNS provider can only stop its own users from receiving a normal answer for a domain.
That makes DNS blocking an access restriction, not content removal. The domain and its content may remain online, while users of the filtered resolver receive an error, empty response or redirected result.
Why France-only blocking conflicts with Quad9’s privacy model
Quad9 says it does not maintain a reliable database of users’ identities or nationalities. That is a privacy feature, but it complicates an order aimed only at people in one country.
An IP address can suggest a location, yet geolocation is imperfect. Mobile networks, corporate gateways, VPNs, satellite services and cross-border connections can make users appear somewhere they are not. Infrastructure may also process requests outside the requester’s country without changing the user’s legal location.
According to Quad9, the order leaves three practical choices:
- Block the domains worldwide. This would extend one national court’s order to users in countries where it does not apply.
- Attempt geographic filtering. Quad9 would need location data and enforcement systems that can make mistakes, increase data processing and undermine its privacy-minimizing architecture.
- Withdraw from France. French requests would no longer use Quad9, avoiding global censorship while protecting the organization from accumulating daily penalties.
Quad9 selected the third option. Its decision illustrates how national blocking mandates can pressure a global service either to redesign itself around surveillance and borders or leave the jurisdiction.
Cloudflare’s criticism of DNS-level piracy enforcement
Cloudflare has argued that court ordered website blocking at the DNS layer is ineffective because users can change resolvers. A block implemented by one provider does not remove the website, revoke its domain or disable its hosting. It changes only the answer supplied by that resolver.
This does not mean blocking has no effect; it can reduce casual access. Cloudflare’s contention is that the effect is limited relative to the legal and technical risks. Those risks include blocking an entire domain when only a page or service is disputed, applying stale lists after content moves, and interfering with legitimate services that share infrastructure or domain names.
DNS-level action can also disrupt security protections. If users abandon a security-filtering resolver because of copyright blocks—or repeatedly move between unfamiliar services—they may lose malware and phishing defenses. Cloudflare further warns that orders directed at public DNS resolvers can create a fragmented system in which identical domain queries produce different results based on provider, court order and assumed location.
DNS over HTTPS and DNS over TLS do not settle the dispute
DNS over HTTPS (DoH) and DNS over TLS (DoT) encrypt DNS traffic between a device and its chosen resolver. This prevents many network observers from reading or altering requests in transit, improving DNS privacy on untrusted networks.
Encryption does not prevent the resolver itself from applying a blocking list. If a public DNS provider is subject to an order, its DoH and DoT endpoints can return filtered responses just as its traditional DNS service can. The policy is enforced after the encrypted request reaches the provider.
The case could nevertheless affect encrypted DNS indirectly. Public resolvers helped make DoH and DoT practical at scale. If providers must identify locations, retain additional information or maintain country-specific rule sets, users may receive less privacy from services originally designed to minimize data collection.
There is also a security concern. Quad9’s voluntary malware blocking is based on technical threat intelligence and a published service purpose. Copyright blocking is based on legal determinations about content. Treating the two as equivalent could gradually turn security resolvers into general-purpose internet censorship systems.
OpenDNS set a precedent—and other providers remain exposed
Quad9 is not the first major resolver to choose withdrawal. Cisco previously discontinued its OpenDNS service in France after facing a sports piracy blocking order. That earlier exit demonstrated that legal pressure can reduce, rather than expand, the DNS choices available to French users.
Google Public DNS, Cloudflare DNS and other public DNS resolvers have also faced litigation or demands connected to France piracy laws. Their scale, architecture and legal strategies differ, so Quad9’s response does not predict that every provider will leave. It does show that operators can be pressured even when they neither host the content nor have a direct relationship with the alleged infringer.
What French Quad9 users should do
People who rely on Quad9 should review their settings before November 24, particularly if DNS was configured manually on a router. A loss of resolver availability can look like an internet outage because applications cannot translate domain names into addresses.
- Identify the current configuration. Check the DNS section of the router, operating system, browser and mobile network settings. Quad9 commonly appears as 9.9.9.9 or 149.112.112.112, while encrypted configurations may display a Quad9 hostname or profile.
- Check for managed settings. Workplace, school, parental-control, antivirus or VPN software may select DNS automatically. Consult the administrator before changing a managed device.
- Choose according to privacy and security needs. Options include the internet provider’s resolver, Cloudflare DNS at 1.1.1.1, Google Public DNS at 8.8.8.8, or another reputable operator. Compare logging, retention, malware filtering, DoH and DoT support, reliability and applicable jurisdiction.
- Use official instructions. Configuration details can be confirmed on Quad9’s official site and, for one alternative, in Cloudflare’s setup documentation.
- Test normal browsing and security controls. Confirm that legitimate sites resolve and that any expected phishing, malware or family-safety features remain active.
Changing DNS should be treated as a connectivity, privacy and security decision—not as instructions for accessing illegal streams or evading lawful restrictions. Users remain responsible for following copyright law regardless of which resolver they select.
Where does this leave DNS neutrality?
DNS has never been entirely free of policy. Security resolvers block malicious domains, family services filter adult material, and network operators respond to legal orders. The crucial questions are who defines the list, whether users knowingly selected that policy, how errors are corrected and whether one country’s decision affects the global namespace.
If public DNS providers become routine copyright enforcement points, they may need more user-location data, larger legal compliance teams and country-specific versions of the internet. Smaller nonprofit operators are least equipped to absorb those costs. The likely result is fewer independent resolvers and greater concentration among companies able to manage worldwide filtering obligations.
The Quad9 France DNS blocking case therefore concerns more than 58 domains. It tests whether recursive DNS remains a neutral, privacy-preserving route to internet destinations or becomes a convenient control layer for disputes that originate elsewhere. Blocking may offer rights holders a rapid remedy, but using DNS as a universal enforcement mechanism can weaken the openness and security that make the system valuable.
Frequently asked questions
Why is Quad9 leaving France?
Quad9 says it cannot implement France-only copyright blocking reliably without adding location-based controls that conflict with its global and privacy-focused design. Worldwide blocking would overextend the court order, while non-compliance carries a €1,000 daily penalty.
Will Quad9 stop working in France immediately?
Quad9 has announced that its free cyberprotection service will be withdrawn from France beginning November 24, 2026. Users should check the nonprofit’s official notices for implementation details or changes.
Does the court order remove the pirate websites?
No. It requires covered DNS resolvers to stop returning normal DNS results for the listed domains. The content, hosting and domain registrations may continue to exist unless separate action is taken against them.
Does encrypted DNS bypass provider blocking?
No. DNS over HTTPS and DNS over TLS protect the request while it travels to the resolver. They do not stop that resolver from applying court-mandated or voluntary filtering.
Is switching to another public DNS resolver safe?
It can be, provided the operator is reputable and its privacy, logging and security policies match the user’s needs. Alternatives may offer different malware protection and may themselves be subject to current or future French blocking orders.