this post was submitted on 12 Dec 2024
142 points (99.3% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
55064 readers
156 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Time to change to ipv6 ip that not change? Then dns not necessary, not even domain registrar.
What even different to go after domain registrar? If domain unregistered, same result as block on all dns globally?
Huh? Dns and ipv4 are two different things. You're probably thinking of NAT.
There so many ipv6 adress no need to change. Dns for get ip from hostname and update ip if change.
Ipv4 not enough adress, so always change, not need with ipv6.
DNS exists so you don't have to learn a bunch of IP addresses. Changing to ipv6 doesn't fix that.
But dns also for dynamic ip. See DynDNS or load-leveling algorithm for choosing CDN in proximity. ipv6 fix that.
That doesn't get rid of the need for DNS. And ipv6 won't get rid of the need to load balance using dns.
Why not? If ip + domain in /etc/hosts and ip not change, what need dns for?
Also can load balance by http 302 redirect if server overloaded. Maybe not as good, but should work?
Because 99.9% of people are not going to maintain a hosts file, and don't even know it exists. Not to mention you'd have to already know the IP of the sites you wanted to visit.
You're basically arguing that phone books are a bad thing because people can just keep an address book.
99.9% of people not use piracy website that will be dns poison. And those website probably start insert guide for /etc/hosts on front page like did for alternative dns.
Not say dns is bad. Just search for solution for dns poison.
And can know ip from dns before poison or from megathread.
BS solution that doesnt apply to the problem.
Problem: The DNS doesnt resolve the domain anymore so https://www.foo.bar/ resolves to 0.0.0.0
Solution: Change domain or directly connect via the IP.
Problem 2: What's the IP if you can't resolve it first. There aint telephone books anymore.
Solution: while not dns block, write down domain + ip in /etc/hosts.
What is megathread then? Put ip there, then do /etc/hosts solution.
I am thinking more about a general "phone book" and not a specialized section in the yellow pages.
Amd connecting to google via IP is not possible. Same for other companies and organizations that utilize obfuscation of the actual servers like reverse proxies and load-balancers.
But we talk about solution for dns poison of website. Not dns death in general.
Huh? We are talking about a dns provider being ordered to resolve a domain.
Oh i talking about solution to dns poison.