4 ms·
The real "complaint" is that Google broke the ISPs ability to highjack your DNS. With that real goal in mind, they will still "complain" if Google wrap DNS on h
by thanhhaimai 6y ago
The real "complaint" is that Google broke the ISPs ability to highjack your DNS. With that real goal in mind, they will still "complain" if Google wrap DNS on https and send to 8.8.8.8
The ISPs now will have a series of PR articles about how Google wants to own the internet, track all your web DNS, monopolize the access, and evil blah blah.
We should read these articles with the mindset that they are PR pieces, not a solution request.
Opinions are my own.
- donor20 6y agoVerisign, the folks complaining did a wildcard DNS entry for ALL .com and .net domains called sitefinder! How can they handle the bandwidth for that (serving full web pages with lots of "partner" offers etc) but not 3 DNS packets? Something doesn't make sense here.
- floatingatoll 6y agoThe budget for operating the root servers is unlikely to be shared with the budget for operating Sitefinder.
- icedchai 6y agoThe GTLD / top level domain servers are different from root servers. Also, root servers are a shared, distributed responsibility. Verisign doesn't run most of them: https://en.wikipedia.org/wiki/Root_name_server https://en.wikipedia.org/wiki/Root_name_server
- hn_check 6y ago"The ISPs now will have a series of PR articles about how Google wants to own the internet, track all your web DNS, monopolize the access, and evil blah blah." They'd be right, but that's neither here nor there in this contrived strawman. And yes, a lot of people would have a serious problem if Google baked in their own DNS. That would break a lot of stuff. And it would make the notion of checking invalid DNS entries rather unnecessary, wouldn't it?
- rootsudo 6y agoI thought it was already the default for chrome?