95
Google Receives Piracy Shield Orders to Block Pirate Sites in Public DNS * TorrentFreak
(torrentfreak.com)
this post was submitted on 18 Jun 2025
95 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
62324 readers
229 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:
Gaming:
💰 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
I mean, as far as I know, DNS is decentralized. Anyone can host their own DNS server, or change which server their network/device uses. Google's is just very commonly used because 8.8.8.8 is easy to remember, but there are thousands of others run by entities big and small, and there's nothing stopping you from running your own (assuming you manage to get a hold of a static IPv4)
This is the correct answer. The only thing I would add is some devices don't allow changing the DNS IPs and are hard coded to 8.8.8.8 so Google blocking sites via DNS is still an issue. Of course you could intercept these requests, but with DNS over HTTPS becoming more popular, i would imagine that device manufactures will also start to do certificate pinning as well to prevent people from using their own DNS server.
Why? Just BC fuck plebs?
the answer is always money.