Hacker News new | ask | show | jobs
by TheRealSteel 1952 days ago
Surely it'd be trivial to increase the user's speed to Netflix servers if they've visited Fast.com in the last three minutes or similar?
1 comments

Thanks to TLS, Netflix and Fast are indistinguishable. All your ISP knows is the IP address you’re talking to. They’d only know that you visited Fast in particular if you were using your ISP’s DNS, which you shouldn’t be using anyways :)
It's indistinguishable from an protocol perspective, not a data analysis perspective. Or to put it more practically, if a large data stream from Netflix lasts more than 10 seconds, it's video.
Except SNI will leak the domain name of the host you are connecting to.
Makes sense, networking was never my strong point. To be fair, alot of people will be using their ISP's DNS, but at least this is avoidable, even if you have to specifically take steps.
Personally I trust my ISP DNS a hell of a lot more than Google/Cloudflare. Why would I want to give them even more data about me?
Wow, where do you live?! Across the US and UK, I’ve consistently found home-ISP-supplied DNS to be slow, spammy and unreliable.
I've had ISP DNS servers that redirect NXDOMAIN responses to spammy "search" pages full of sponsored crap and banner ads.

There's always OpenNIC, DNS.watch, or Quad9 if you're after something that isn't operated by a creepy megacorp.