6 ms·
I wonder if the only change that needs to happen is that applications driving a significant amount of traffic (i.e. Chrome) & DNS owners of other domains need t
by vlovich123 6y ago
I wonder if the only change that needs to happen is that applications driving a significant amount of traffic (i.e. Chrome) & DNS owners of other domains need to start bearing the costs here. Then we wouldn't be dealing with cost externalities & tragedy of the commons. On the other hand, introduce revenue streams & you start focusing on optimizing the revenue stream instead of solving the problem.
I wonder if there's a different way to make the costs felt that isn't directly revenue to align incentives. Like slow down or fail queries for zones who's authoritative servers don't implement the features needed to keep scaling under control. Then make sure that there's revenue to the root servers from non-root servers based on load so that costs are tracked & managed.
- temp667 6y agoJust let google run some of the roots - I'm serious. For all the whining about bandwidth and traffic, this issue is so small on the scale of google (which includes youtube) and netflix traffic flows it's hard to even imagine. Their secondary resolvers run at huge volumes, everything from 8.8.8.8 to the dns for their mail and other web properties.
- jeffbee 6y agoThe problem is it does not help to have one or two fast roots. The root server model only really works when the roots each have similar capacity.
- temp667 6y agoA root is not one static machine. Google can serve 1/3 of traffic for all routes, AWS could do the same. I don't think folks realize how SMALL the root dns traffic is. Youtube / netflix / amazon prime video are just orders and orders of magnitude more demanding in terms of bandwidth - every second they are pumping MULTIPLE HD streams to millions of folks. They measure bandwidth terrabits per second. Even at 30 frames per second, we are talking incredible bandwidth. DNS responses should be 1K or less (often .5K). About 40 netflix viewers at their top quality use the same bandwidth? Netflix has far more than 40 users.
- jeffbee 6y agoYou think the root operators should just delegate part of the traffic of all letters' VIPs to google and amazon? It's not crazy, but it would mean the entire root would have a shared-fate failure mode.
- tremon 6y agoI don't understand. What's the failure mode you're thinking of?
- jeffbee 6y agoSomeone at Google pushes yet another invalid config of death, taking out their global network and, with this proposal, also taking down 1/3rd of all DNS root capacity.
- temp667 6y agoYou could easily 3x provision root dns (or more). I'm just pointing out that for all the complaining about google efforts to block domain jacking (which was endemic before they started their efforts) scaling the root is doable, and if the existing maintainers are too incompetent to scale it then maybe others should be allowed to. I mean, how do they handle denial of service attacks which are going to be orders of magnitude higher in volume? The logic here is so warped. https://www.digitalinformationworld.com/2020/08/a-major-bug-in-google-chrome-is-causing-a-massive-load-on-global-root-dns-servers.html https://www.digitalinformationworld.com/2020/08/a-major-bug-... Rather than the solution being to allow for domain hijacking by turning off the redirect detectore, how about verisign, which kicked this whole thing off recently AND way back with their "sitefinder" garbage get a clue and either propose another solution to domain jacking or scale the root a bit.
- DenseComet 6y agoThere already is precedence for this. Cloudflare provides a huge chunk of F-root servers. https://blog.cloudflare.com/f-root/ https://blog.cloudflare.com/f-root/
- JdeBP 6y agoYou've conflated the proxy DNS servers, that do grunt work of query resolution (or forward to other proxies that do), with the content DNS servers. It is not the content DNS servers that are causing the scaling problems, it is the proxy DNS servers, and the DNS clients and applications softwares that drive them. * http://jdebp.uk./FGA/dns-server-roles.html http://jdebp.uk./FGA/dns-server-roles.html The change that needs to happen is the thing that most people nowadays tell one first, that this paper in contrast leaves all of the way to the end: run your own content DNS server(s) for the root, on your own LAN or Intranet. It's fairly simple to do, and it's an idea that has been around for over two decades, now. * https://news.ycombinator.com/item?id=24277855 https://news.ycombinator.com/item?id=24277855 * https://news.ycombinator.com/item?id=19526108 https://news.ycombinator.com/item?id=19526108 * http://cr.yp.to/dnsroot.html http://cr.yp.to/dnsroot.html (dates back to 2001) * https://news.ycombinator.com/item?id=24280536 https://news.ycombinator.com/item?id=24280536 et al. It takes a long time in the DNS world for such grassroots ideas to percolate to the level that they get circulated by corporate officers. This article is, for example, still propounding that every resolving proxy DNS server works like ISC's BIND, and has a "priming query". This is untrue in reality, and is one of the differences between BIND and some of the softwares (e.g. dnscache and MaraDNS) that came along to replace it a couple of decades ago. * https://maradns.samiam.org/faq.html#roothints https://maradns.samiam.org/faq.html#roothints Similarly the argument that Google should use a subdomain, presented in this article without any counterpoint at all, has long since been countered by pointing out that this makes the malicious actors' lives easier; as conditional forwarding and split-horizon DNS service, which are well-known things, would then make it easier to fool Google Chrome. And there have been other counterarguments made, years ago. * https://news.ycombinator.com/item?id=3609498 https://news.ycombinator.com/item?id=3609498 (yes, 2012)
- dkdk8283 6y agoI think your terms are incorrect. Proxy queries in your context are referred to as recursive and content is authoritative.
- JdeBP 6y agoThese aren't types of query, they are types of server. viovich123 was talking about content DNS servers that cause the scaling problems, and penalizing the people who run them. But it is the proxy DNS servers, and the DNS clients and applications softwares that drive them, that are the cause here. The terms are correct, and are derived from HTTP. You aren't grasping them correctly.