this post was submitted on 05 Apr 2026
138 points (98.6% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

70298 readers
917 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

We heartily recommend visiting the free port of freemediaheckyeah (aka FMHY) while you sail the high seas, for all the freshest links the ocean has to offer.

📜 c/Piracy Wiki (Community Edition):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 3 years ago
MODERATORS
 

Last week's Supreme Court decision in Cox Communications reshaped the piracy liability landscape, creating new urgency for site-blocking.

you are viewing a single comment's thread
view the rest of the comments
[–] dan@upvote.au 9 points 4 months ago* (last edited 4 months ago) (1 children)

Best solution is not using dns in the first place though.

Use DNS over HTTPS (or TLS or QUIC). I think some browsers use it by default now. If there's country-specific blocks, use your own recursive DNS server, or one in another country.

[–] Teknikal@anarchist.nexus 1 points 4 months ago* (last edited 4 months ago) (1 children)

Can still be messed with by the Isp not saying dns encrypt is a solution but it will bypass this, not much it can do against direct IP blocking mind you for that you need vpn or a service like tor/i2p.

Does stop the this has been blocked by court order type messages though and does it well.

[–] dan@upvote.au 1 points 4 months ago

Can still be messed with by the Isp

Not as easily though. It's like regular HTTPS - if anyone, including the ISP, tries a MitM (man in the middle) attack, you'll get a security error because the certificate won't be trusted. The only real way for a MitM attack to be successful is installing a custom root certificate on the client system.

Like you mentioned, IP blocking is harder to bypass, but that's unrelated to DNS blocking. IP blocking is harder to do if the site uses a CDN like CloudFront, BunnyCDN, Cloudflare, etc though, since a large number of sites use the same IPs.