Hacker News Reader

I'm looking into this a bit more for some basic math.

It looks like QPS is around 1.3M per second? Am I way off? What the bandwidth? I'm getting 1GBps or less which seems pretty low?

If the root can't handle this how does it handle DOS floods even?

Should we just turn some of the root over to some of the bigger players that can actually scale (AWS / GCP / Azure / Netflix etc)? These rates seem so small for this level of complaining about google et al.

View on HN

Yeah, the conclusion I'm getting is, how do I sign up to be a root? Chrome's NXDOMAIN detection is good for the world and it sounds like handling 50% of root server traffic would not be that hard.

Digging a bit more it looks like some of just the public DNS servers are doing WAY more traffic than this. Google was doing 810K qps on 8.8.8.8 alone in 2012 (8 YEARs ago).

Can't they offer to operate some of the root zone then if it's so hard for these other folks to manage it (maybe do something with AWS / Azure etc).

As of the first graph in this August 2018 blog post [0], it seems like Google's Public DNS was handling about 14-18M QPS (1.2-1.6T per day).

[0] https://security.googleblog.com/2018/08/google-public-dns-tu...

Reply on news.ycombinator.com