178
Google, Cloudflare & Cisco Will Poison DNS to Stop Piracy Block Circumvention * TorrentFreak
(torrentfreak.com)
this post was submitted on 16 Jun 2024
178 points (99.4% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54746 readers
222 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):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Apparently Cisco operates a popular DNS resolver? Never heard of that before.
And definitely don't learn how to use a VPN. Or set up Unbound or Bind or PowerDNS Recursive...
Cisco bought OpenDNS a few years ago,
Ah crap, good to know. This sucks though, I was thinking of using it to replace CF. What's left? Quad9 and the unbound type?
Uncensoreddns is a great alternative.
ATM I'm using Quad9 and OpenNIC but I'm not sure how much of everything do they cover. I'm also not well aware of any other good "flat DNS" alternative (aka: one you can put right into your /etc/resolv.conf / Windows LAN config, without need of extra internal service).
Cisco operates from the ISP side, they'll poison DNS through their routers. And you should be aware that your ISP will employ Deep Packet Inspection which can also be done with Cisco routers. That means they can intercept internet traffic, especially if your internet connection is not encrypted.
Guess ill be trying my hand at building my own pfsense router
ISPs were already required to block the sites. I don't think an additional block on the Cisco side would change anything in that case.