Introduction
On October 22, 2026, Swiss non-profit Quad9 announced it would cease operations in France, effective November 24. The trigger: a ruling by the Paris civil court ordering the public DNS resolver to block around fifty domains linked to illegal streams of tennis matches, at the request of beIN Sports. Quad9 refused — not as a matter of principle, but for a reason rooted in its own data architecture. It simply does not hold the information required to comply in a geographically targeted way.
A Geographic Block That Requires Data Quad9 Never Collected
Quad9 runs a public DNS resolver at 9.9.9.9 — free, no account required. That design choice is precisely what makes the injunction unenforceable. Selectively blocking certain domains for French users requires, at minimum, a geolocation mechanism for incoming queries and an IP-to-territory mapping database. Quad9 built its entire model on the deliberate absence of such data: no IP address logs, no user profiles, no query traceability. This is an intentional architectural decision, positioned as a privacy guarantee and as full GDPR compliance.
The alternative — blocking the contested domains globally, across its entire worldwide user base — was ruled out as disproportionate. Rather than build from scratch a database it had always refused to maintain, or apply a worldwide block on the order of a single national court, Quad9 chose to stop serving French territory. The initial penalty beIN Sports sought reached €580,000 per day; the court reduced it to €1,000 per day. That reduction did not change the foundation's position, which is also facing around twenty other active legal proceedings in France.
What Your DNS Layer Says About Your Data Governance
This case is more than an isolated legal dispute. It exposes a category of decisions that many IT teams never formally document: the choice of DNS resolver.
DNS is the first layer of every network connection. Every data pipeline, every third-party API call, every SaaS sync starts with a name resolution. Who handles that resolution, what data they retain, and under which jurisdiction they operate — these questions have direct implications for the operational data sovereignty of any organisation.
Quad9 was used across institutional networks — healthcare, education, local government, energy — for two properties it delivered simultaneously: active filtering of malicious domains fed by more than twenty-five threat intelligence providers, and zero user logging. Its withdrawal from France leaves a functional gap for these organisations, which will need to migrate to an alternative resolver or deploy one in-house.
Three Questions to Ask About Your DNS Stack
Does your current resolver collect data? Many IT teams do not know whether their resolver logs queries, stores them locally, or forwards them to a third party. Yet this is operational data covering every application flow in the organisation — data that rarely appears in processing maps.
How dependent are you on a third-party service? If a public resolver goes dark or changes its policy, how many systems quietly fall back to an undocumented fallback configuration?
How does your DNS align with your sovereignty strategy? The European Union launched DNS4EU in 2025, a resolver built to meet European regulatory requirements. On-premise solutions offer full control over logs and filtering rules, at the cost of internalised operational management.
The Quad9 case illustrates a tension that is becoming a recurring theme in data governance: architectures designed to minimise data collection are highly effective for privacy, but can collide with legal obligations that presuppose the very existence of that data. This is a trade-off that CIOs and data leaders need to document explicitly — not leave frozen by default in an inherited network configuration.