---
type: "post"
id: "quad9-s-withdrawal-from-france-a-canary-in-70482e"
slug: "quad9-s-withdrawal-from-france-a-canary-in-70482e"
title: "Quad9’s withdrawal from France: A canary in the coal mine"
description: "Quad9 says it will withdraw its free public DNS resolver from France after a court ruling imposed daily financial penalties for failing to block domains associated with alleged copyright infringement."
retrieval_nugget: "Quad9 says it will withdraw its free public DNS resolver from France after a court ruling imposed daily financial penalties for failing to block domains associated with alleged copyright infringement. The case shows how enforcement aimed at one layer of the internet can instead drive a privacy-focused infrastructure provider out of a country, leaving users to manage the disruption."
published_at: "2026-11-18"
updated_at: "2026-11-18"
record_date: "2026-11-18"
date_kind: "published_at"
topics: ["google"]
entities: ["Quad9","Cloudflare","OpenDNS","Google","Cisco","DNS4EU"]
related_patterns: []
novelty_label: "new_fact"
what_changed: "Cloudflare says Quad9 has withdrawn from France, warning that the case signals broader risks for DNS resolvers facing blocking demands."
prior_refs: []
source_url: "https://blog.cloudflare.com/quad9-withdrawal-from-france"
source_urls: ["https://blog.cloudflare.com/quad9-withdrawal-from-france"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:quad9-s-withdrawal-from-france-a-canary-in-70482e"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/quad9-s-withdrawal-from-france-a-canary-in-70482e/","markdown":"https://newruntime.com/posts/quad9-s-withdrawal-from-france-a-canary-in-70482e.md","json":"https://newruntime.com/posts/quad9-s-withdrawal-from-france-a-canary-in-70482e.json"}
markdown_url: "https://newruntime.com/posts/quad9-s-withdrawal-from-france-a-canary-in-70482e.md"
---

# Quad9’s withdrawal from France: A canary in the coal mine

## Retrieval answer

Quad9 says it will withdraw its free public DNS resolver from France after a court ruling imposed daily financial penalties for failing to block domains associated with alleged copyright infringement. The case shows how enforcement aimed at one layer of the internet can instead drive a privacy-focused infrastructure provider out of a country, leaving users to manage the disruption.

## Summary
Quad9 says it will withdraw its free public DNS resolver from France after a court ruling imposed daily financial penalties for failing to block domains associated with alleged copyright infringement. The case shows how enforcement aimed at one layer of the internet can instead drive a privacy-focused infrastructure provider out of a country, leaving users to manage the disruption.

## What happened
Cloudflare’s November 17, 2026 announcement says Quad9, a Swiss non-profit foundation, announced the previous month that it would withdraw its free public DNS resolver from France. The decision followed months of litigation and a French court ruling imposing daily financial penalties on Quad9 for failing to block domains associated with alleged copyright infringement. Cloudflare describes Quad9 as having faced a choice between continued litigation and penalties or changing its service in a way that would undermine user privacy and security. Quad9 chose to leave France.

A DNS resolver translates a domain name, such as a website address typed by a user, into the IP address needed to connect to it. People use resolvers run by internet service providers, mobile networks, businesses, universities, or public services such as Quad9’s 9.9.9.9. Cloudflare’s account says a resolver can block a domain by declining to return its IP address, but cannot remove the underlying content or take down the server hosting it. Users can bypass a resolver-level block by switching to another resolver, or by using the site’s IP address directly. Cloudflare says there is no evidence such public-resolver blocking reduces the total amount of online infringement.

The company also argues that resolver blocking is blunt: DNS works at the domain level, so blocking one domain can affect both lawful and infringing material hosted there. The failure is opaque to users, who may see only that a site will not load. Public resolvers operate across borders, so an order in one country can affect access beyond it. Cloudflare says attempts to localize blocking would alter resolver services in ways that could harm performance, resilience, privacy, and the open internet.

Cloudflare says Quad9 cannot directly notify its French users before the withdrawal because its privacy-preserving service does not identify them. It warns that people and organizations—including hospitals, universities, government bodies, and utilities—may find that internet access stops working if their devices continue to use Quad9. The announcement cites Cisco’s earlier withdrawal of OpenDNS from France, Portugal, and Belgium temporarily, and a Belgian court order that could impose penalties unless Cloudflare, Google, and Cisco begin blocking websites through their public resolvers by early January 2027. Cloudflare says it has appealed that order with Google and Cisco. It advocates addressing piracy through hosting providers that store infringing files rather than public DNS resolvers.

## What the archive adds
New Runtime’s earlier coverage connected DNS to agent containment: [an agent used DNS to reach an external chatbot](https://newruntime.com/posts/an-agent-used-dns-to-reach-an-external-1a597a/) (October 1, 2026). That was an incident about network access in an agent environment; this is a new event about court-ordered blocking and the availability of a public resolver in France.

## Trend signal
This does not yet fit a pattern New Runtime tracks. The announcement describes a dispute over public internet infrastructure and jurisdiction, not a change to agent runtimes, protocols, or software capabilities.

## Why now
The immediate trigger is Quad9’s planned French withdrawal following the court’s financial penalties. A second deadline is approaching: Cloudflare says a Belgian order could impose penalties unless three public resolver providers begin blocking websites by early January 2027. The timing makes the French case a live signal of whether similar demands will spread to other resolver operators.

## Connections to other events
New Runtime’s earlier coverage of an audit of third-party sandboxes found that network confinement can fail independently of virtual-machine isolation ([October 21, 2026](https://newruntime.com/posts/audit-of-10-third-party-sandboxes-found-8-54fdd3/)). The cases concern different systems and risks, but both underline that network behavior is a consequential infrastructure boundary: here, court orders target what a resolver returns; in the audit, the question was whether sandboxed agents could reach destinations beyond their intended boundary.

## Why it matters
For teams building AI products, DNS can be easy to treat as invisible plumbing. But applications, agents, devices, and internal services depend on name resolution to reach APIs, model providers, data sources, and control planes. A resolver change can therefore become an availability or security event even when the application itself has not changed. The French case also illustrates that a legal or policy decision at an infrastructure layer may have consequences for users who did not choose the dispute and may not know which resolver their devices use.

This is not evidence that AI services will be blocked in France, nor does it establish that DNS blocking will disrupt any particular AI workload. It is a reminder to make dependencies observable: document resolver configuration, identify whether it is centrally managed or hard-coded, and know how to change it safely. For organizations running critical systems, DNS should be included in continuity planning alongside connectivity and identity services. The practical lesson is not to predict a specific outage, but to avoid discovering an invisible dependency only after it stops working.

## Limits and uncertainty
Cloudflare is an interested participant: it operates a public resolver and says it opposes mandated blocking. Its account provides its description of the French ruling and the effects it expects, but does not reproduce the judgment or provide Quad9’s own detailed implementation schedule. The announcement does not quantify how many French users or institutions rely on Quad9, when service will stop, or how many will be affected. The claimed lack of evidence that blocking reduces infringement is Cloudflare’s characterization; the announcement does not present the underlying study or its methodology. The Belgian proceedings also remain unresolved in this account, so their eventual scope and consequences are uncertain.

## Reader takeaway
A DNS resolver is a policy and availability dependency, not just a speed setting. Quad9’s planned exit from France makes that visible: users and organizations that rely on a public resolver may face disruption when legal pressure changes where it operates. Builders should know which resolver their systems use and how that dependency would be changed or communicated if service ends.

## Open question
How many French organizations will discover that Quad9 is embedded in their network or device configuration only after its resolver stops serving them?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Google](https://newruntime.com/topics/google.md): Explore the google topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
