Hacker News Reader

Given that ISPs like to play with traffic and have been using censoring DNS servers again and again I can't blame Google for taking away one piece of potentially failing networking infrastructure and using their own.

It's not nice, but it's not Google who started this.

View on HN

You are missing the point, it's not that they first try 8.8.8.8 then falling back to ISP/defaults, they are requiring 8.8.8.8 for DNS which is BS.

If they would fallback to the ISP's DNS server they'd encourage the ISP to block access to their DNS, which arguably would be even worse.

Honest question: is that even legal?

In the US? Oh man, it's even worse than that. ISPs can probably legally choose to block whatever, including editorially blocking content they find offensive. Your ISP could legally choose to just start blocking port 443 because they want to make sure you're not looking at anything inappropriate. Comcast will straight up mutate HTML content sometimes to insert their own JavaScript: https://news.ycombinator.com/item?id=15890551

What happens when all DNS but the ISP's is blocked? I've been in many a corporate and cheapo Internet situation like this.

Reply on news.ycombinator.com