this post was submitted on 16 Aug 2025
108 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
63572 readers
329 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
🏴☠️ Other communities
FUCK ADOBE!
Torrenting/P2P:
- !seedboxes@lemmy.dbzer0.com
- !trackers@lemmy.dbzer0.com
- !qbittorrent@lemmy.dbzer0.com
- !libretorrent@lemmy.dbzer0.com
- !soulseek@lemmy.dbzer0.com
Gaming:
- !steamdeckpirates@lemmy.dbzer0.com
- !newyuzupiracy@lemmy.dbzer0.com
- !switchpirates@lemmy.dbzer0.com
- !3dspiracy@lemmy.dbzer0.com
- !retropirates@lemmy.dbzer0.com
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Maybe it includes dns. Using quad9 would bypass this.
I bumped into at least one site blocked by cloudflare. When accessing the site, I'm redirected to:
https://www.cloudflare-terms-of-service-abuse.com/stream.ts
So far it happens when I try the landing page of the site, if I go pages I visited in the past I can reach the intended site. Maybe the name resolution is cached.
I haven't tested it much but I'm using Quad9 and it's not making any difference.
Cloudflare seems to be the SOA for the affected sites and then it sets *.ns.cloudflare.com as the primary source and dns.cloudflare.com as the administrator.
To my understanding Quad9, being a recursive DNS resolver, is not the main DNS authority in this case. Quad9 will reach out to cloudflare to refresh the records when the TTL expires and then cloudflare can return a different IP for the domain.
Either affected sites stop using cloudflare, or we reach them via TOR, if they have that option.
It happened to me once with 1337x redirecting to that stream.ts, i deleted the prepending "www." and it worked again.