Re:A Chrome feature is creating load on global root DNS servers
by donor20 on Tuesday August 25, 2020 @05:47PM
(#24276555)
Verisign, 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.
Re:A Chrome feature is creating load on global root DNS servers
by floatingatoll on Tuesday August 25, 2020 @06:22PM
(#24276927)
The budget for operating the root servers is unlikely to be shared with the budget for operating Sitefinder.
Re:A Chrome feature is creating load on global root DNS servers
by icedchai on Tuesday August 25, 2020 @07:28PM
(#24277465)
The 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
Re:A Chrome feature is creating load on global root DNS servers
by hn_check on Tuesday August 25, 2020 @09:03PM
(#24277997)
"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?
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.