Re:Chromium's impact on root DNS traffic (2020)
by tptacek on Wednesday February 08, 2023 @08:07AM
(#34707463)
That doesn't at all seem like what happened (the changes were in the works prior to the drama), but this is a high-drama tangent unrelated to the story here.
This isn't some tiny authoritative DNS server being flooded unexpectedly with queries. These are the Internet DNS root services. They have to keep up with this kind of traffic. It's their literal job description.
Re:Chromium's impact on root DNS traffic (2020)
by adql on Wednesday February 08, 2023 @09:54AM
(#34708799)
To be fair, that's less than one a second.
But I dislike the whole GOPROXY design, like it breaking private repos by default and having to set some env variables to make this stupid tool download stuff from server I told it to download.
Re:Chromium's impact on root DNS traffic (2020)
by capableweb on Wednesday February 08, 2023 @10:06AM
(#34708994)
> To be fair, that's less than one a second.
Well, taking the context into consideration, I'd still say it's too much. Context being they were full git clones and the traffic ended up representing "70% of all outgoing network traffic from git.sr.ht".
Reminds me of the recent "Go module mirror fiasco" where Google found it fair to clone repositories at a rate of ~2,500 per hour in order to essentially proxy Go modules.
- "Sourcehut will blacklist the Go module mirror" - https://news.ycombinator.com/item?id=34310674
After the drama become very much public, they finally decided to address the issue in a good way.