DNS resolvers are the wrong place to fight piracy
- ID
- 47974
- Status
- summarized
- Published
- 18 Nov 2026, 9:18 PM
- Fetched
- 19 Nov 2026, 5:09 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 19 Nov 2026, 5:10 AM
- Tags
- Audience
- developerssaas_founders
What happened
Quad9, the Swiss non-profit behind the 9.9.9.9 public resolver, will stop answering DNS queries from France on Tuesday, November 24, 2026 — not over cost or users, but because a Paris court fined it for refusing to block a list of pirate sports-streaming domains on behalf of beIN Sports, with roughly 20 similar cases still pending. Quad9 filters malware/phishing domains by design, keeps no user records, and claims 670 million+ blocks a day across 230+ resolver clusters in 110+ countries; its announcement lists French networks it serves including DINUM, RENATER, EDF, SNCF, AP-HM hospitals in Marseille, Thales and Airbus's Stormshield — and it has no way to notify them. Cloudflare (1.1.1.1) called the exit 'a canary in the coal mine', and in the 474-point / 160-comment Hacker News thread Quad9 CTO John Todd asked readers to send long-form, sourced arguments to policymakers.
Why it matters
If you or your users hardcode 9.9.9.9, you lose malware filtering in France on 24 Nov 2026 with no notice — Quad9 explicitly cannot tell the networks it serves it is leaving. The Mullvad case in the article is the concrete failure pattern: Mullvad shut its own encrypted DNS service on 2 Nov 2026 and moved Mullvad Browser defaults to Quad9, so French users were migrated to a resolver that disappears three weeks later. Check your resolver fallback chain now, and treat resolver-level blocking as a design assumption if you ship into markets with site-blocking regimes, rather than an edge case.
Discussion angle
Walk through your own resolver dependency chain live: which of your services, CI runners, VPNs or browser defaults point at 9.9.9.9 or a single filtered resolver, and what actually alerts you if that resolver stops answering for one country?