Scaling the Root of the DNS

Re:Scaling the Root of the DNS by jeffbee on Sunday October 04, 2020 @01:10PM (#24680554)

You 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.

[ Parent | on HN ]

Re:Scaling the Root of the DNS by DenseComet on Sunday October 04, 2020 @03:41PM (#24681708)

There already is precedence for this. Cloudflare provides a huge chunk of F-root servers.

https://blog.cloudflare.com/f-root/

[ Parent | on HN ]

Re:Scaling the Root of the DNS by jeffbee on Sunday October 04, 2020 @04:18PM (#24681972)

Yeah, and it makes perfect sense for these big tech cos to run all or some of one root letter. But it violates the spirit of resilience to have one company participate in multiple letters.

[ Parent | on HN ]

Re:Scaling the Root of the DNS by JdeBP on Monday October 05, 2020 @03:08AM (#24685271)

Like Verisign does, ne? (-:

[ Parent | on HN ]

Re:Scaling the Root of the DNS by tremon on Sunday October 04, 2020 @01:51PM (#24680839)

I don't understand. What's the failure mode you're thinking of?

[ Parent | on HN ]

Re:Scaling the Root of the DNS by jeffbee on Sunday October 04, 2020 @01:53PM (#24680857)

Someone 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.

[ Parent | on HN ]

Re:Scaling the Root of the DNS by temp667 on Tuesday October 06, 2020 @01:49PM (#24700481)

You 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-...

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.

[ Parent | on HN ]