If anything, I am more surprised that Google <i>did</i> comply with the order. The entire value of 8.8.8.8 lies in it being operated as a neutral and independent resolver. If they start returning bogus results for this, what's preventing them from returning bogus results for queries which are inconvenient to their other business units like Youtube? They <i>clearly</i> already have the infrastructure in place to falsify results on a country level...<p>And it'll of course open the floodgates to all kinds of government abuse. This time it's a French court order concerning copyright infringement, next time it might be a kangaroo court ordering Facebook to be blocked because of "political propaganda harming national security".
A good day for the lawyers pay packet<p>A frightening attempt to control DNS providers.<p>How are they going to stop public DNS servers? like OpenNic and others or people who set up their own.<p>There are thousands of DNS providers all over the world.<p>VPN also provide their own DNS servers so maybe the next assault on our freedoms will be VPN.
So if I have a recursive nameserver then it will just get the correct answers from the TLD nameservers.<p>Unless the courts start legislating what people can run in their homes that will ignore any of these rulings.
Why do courts do stupid things like this. It's easy to distribute a HOSTS file with the same information. Are they going to forbid that too?<p>The only people inconvenienced by this will be those who were only casually interested anyway.
Of the 3 I wouldn't have expected Cisco to be the first to take a stand. Well done them.<p>DNS blocking bullshit is especially bad in Portugal because the law is set up in a way that has copyright interest groups just send their block lists directly to ISPs without any kind of judicial process or review whatsoever. It's common knowledge here to change your DNS provider to bypass the ISPs for this reason.
What would be the repercussions of everyone switching to per-site/customer caching, recursive resolvers instead of per ISP resolvers?<p>On the one hand if we assume the customer to ISP ratio to be about a million to one then the volume of traffic on popular nameservers is going to go up a huge amount.<p>On the other hand thoughif your nameserver is now required to handle millions more queries per second then either you are a central piece of infrastructure like .com or a high traffic service like cat.videos.example.com. With the latter, you’ve been handling millions of HTTP queries per second anyway. You’ll just have to handle massive traffic volumes for DNS now, too.<p>The end user is accustomed to the DNS part taking 10ms and tbd HTTP part taking 1000ms. They would probably now have to suffer the DNS part taking 100ms to 1000ms as well.
So if someone from france asks me where a cafe selling marijuana in amsterdam is, and I tell them the address, that's illegal?<p>Oh wait, the internet is special.