ForgeNEX

Quad9 withdraws from France: court-ordered blocks reach DNS

Quad9 leaves France after fines for not blocking pirate domains. A warning for SMEs: if your network depends on a public DNS, you could be left without Internet.

5 min read

In this article

When a judge targets DNS, not content

The news that has shaken the sector this week does not come from a security breach or a software flaw, but from a court decision. Quad9, the Swiss non-profit foundation that operates the public DNS resolver 9.9.9.9, has decided to withdraw its service from France after months of litigation. A French court required it to block domains linked to alleged copyright infringements and imposed daily fines as long as it did not comply. Faced with the dilemma of facing ruinous litigation or altering a service designed to protect the privacy of its users, Quad9 has chosen to leave.

Cloudflare has covered the case on its official blog and describes it as a warning for the rest of the sector. The company recalls that the Swiss foundation found itself caught between two evils and that its departure is "both disheartening and understandable." The important detail for any company is that this type of pressure no longer stays at the content level: it reaches a basic piece of Internet infrastructure.

Illustrative detail: Court-ordered piracy blocks are already affecting essential Internet infrastructure

What a DNS resolver is and why it matters so much

A DNS resolver is the service that translates the domain names we type into the browser into the IP addresses that devices need to connect. Cloudflare sums it up with a very clear image: "DNS is the Internet's address book." When a judge orders a domain to be blocked, the only thing a resolver can do is stop returning that address. The original content remains intact on the network; it is simply hidden from whoever uses that specific resolver.

The problem appears when that resolver operates on a global scale. This is the case with the main public services: Quad9's 9.9.9.9, Cloudflare's 1.1.1.1, Google's 8.8.8.8 or Cisco's OpenDNS. An order issued by a single country can end up affecting users halfway around the world. The European resolver DNS4EU, operated by Whalebone, already applies its blocks by country jointly across the entire European Union, even though the court order behind them may affect only one specific territory. Fragmenting the service to block only in one country, Cloudflare warns, would harm the performance and privacy of the rest of the users.

Who is left without service by Quad9's departure

Quad9's resolver is used in France by government agencies, educational centers, hospitals and public utility companies, as well as by individuals. And here comes the fact that should set off every alarm in any IT department: Quad9 cannot directly notify those institutions that its service is going to stop working. It is a public and open DNS service, with no user registration, so it does not have a channel to contact those who have it configured on their networks.

If those organizations do not change resolver before the shutdown, Cloudflare warns, "their Internet connection will stop working without any explanation." Any device with that resolver configured can no longer translate domain names into IP addresses: the physical connection to the network is still there, but the system does not know which server to direct each request to, so pages do not load. A hospital or a university that uses Quad9 on its internal network would see access to web applications, email or external services fail without any message explaining the cause.

This is not the first time it has happened. Cisco already withdrew its OpenDNS resolver from France and Portugal, and temporarily also from Belgium, in the face of similar court pressure. Quad9 thus joins a list of public DNS operators that prefer to shut down service in a country rather than alter its operation to comply with blocking orders that, according to Cloudflare, do not remove the infringing content: they only hide it from whoever uses that specific resolver.

What this means for a Spanish SME

At first glance, the French case seems distant. But it is worth reading with perspective. In Spain, LaLiga has long pursued the blocking of domains associated with the broadcasting of sporting events, and DNS blocking orders are already part of the legal landscape. If this type of measure extends to the major public resolvers, the scenario that today affects France could be reproduced here with other operators. And an SME that depends on an unsupervised public DNS would find out when its employees cannot open their email.

The lesson is not alarmist, it is operational: name infrastructure is as critical as the router or the firewall, and it is often the least reviewed. At ForgeNEX we see it every week in audits: there are companies that configured a public DNS in DHCP years ago and no one has looked at it again.

Concrete recommendations

  1. Inventory the DNS resolvers in use. Review which DNS servers are configured on the devices, the router, the firewall and the servers. Do not assume you are using your provider's.
  2. Do not depend on a single public resolver. Configure at least two trusted resolvers, ideally one of your own or your connectivity provider's and another as a backup.
  3. Consider a managed or in-house resolver. For networks with critical services, an internal DNS with controlled forwarding avoids surprises and allows you to audit what is blocked and why.
  4. Document the change. If tomorrow an operator announces its withdrawal from Spain, the team should know in minutes which devices are affected and how to replace it.
  5. Review the configuration after incidents. A DNS resolution failure is often confused with an Internet outage. Having a clear procedure saves hours of diagnosis.

This case fits with an idea we have already defended on other occasions: security and availability depend on details that are not always in the spotlight. We saw it with the warning about SHA pinning and with the flaws fixed by patches such as those in WordPress 7.1.5. Basic infrastructure rarely makes headlines until it fails.

A court-ordered block issued in one country can leave users halfway around the world without service. The question for an SME is not whether it will be affected, but whether it would know how to detect and correct it in time.

Quad9's withdrawal from France is not an isolated case, but the tip of a broader conflict between judicial compliance and the open architecture of the Internet. For an SME, the practical conclusion is simple: review today how your devices resolve names and make sure you do not depend on a service that tomorrow may disappear without warning.

Source: RedesZone. Analysis and adaptation: ForgeNEX.

Keep reading

Call us WhatsApp