The beginning of the end of the DNS

Or how the insanely stupid anti-piracy lobby will screw us all

Many of us saw this coming a long while back. Letting the **AA-holes misuse the DNS system for their censoring inevitably leads to the rise of a parallel DNS system. Yes, we already have the darknet for (other) illegal purposes, but this brings the darknet principle into the mainstream in a big way. 

“The censorship is easy to bypass, by simply changing your name server, so we decided to practice what we preach and offer such a service to all those affected by the problem,”


“The Pirate Party’s DNS has added benefits though, as it supports additional Top Level Domains including .geek or .pirate, and the Namecoin based .bit.”

It’s easy to see that this unregulated DNS system will quickly overlay existing domains with alternatives, either accidentally or intentionally. Phishing and DNS MITM attacks will be of an entirely new caliber. The actual “” will lead to a phisher. 
(My prediction for what happens then: with https becoming enforced, the **AA-holes will take control of who can have a cert, leading to the pirates providing new CA roots for users, leading to even the phisher having extended certs… hey ho, there we go.)
Any safeguards built into DNS clients will be switched off by the users wanting to get the “uncensored” internet. 
Can you imagine how hard it will be to convince users to responsibly switch between the public DNS and their respective alternate DNS systems depending on what they’re doing? If there even was any OSs that supported such domain-dependent switching to begin with.
Even if Microsoft, Apple, and Google would want to implement a dual (triple?) DNS client in their systems, the **AA-holes will certainly fight even that, since it would “enable piracy”.
No, I don’t blame the Norwegian Pirate Party for setting this up. I blame the anti-piracy lobby, and the politicians that take their money, for creating the “need” for these destructive designs. Can’t anyone stop them?

Leave a Reply

Your email address will not be published. Required fields are marked *