The owner of the domain is responsible to make sure they are in control of the zone where they've decided to point the name servers. Failure to do so means that

The owner of the domain is responsible to make sure they are in control of the zone where they've decided to point the name servers. Failure to do so means that anyone able to create zones on these name servers can do so. On Amazon you can request a delegation set, which means a combination of four name servers. Do that enough times and I'm sure you'll have all the possible variations that could exist. For every Amazon account you can request 100 delegation sets, but it's easy to scale this out over multiple accounts. I'm also willing to bet you can easily get that limit raised to thousands of delegation sets by just telling support you're going to use the account for hosting tons of zones. I don't know the specifics of how CloudFlare does it, but I assume you're more than welcome to do the same, programatically. There's no hill to die on. I don't work for a provider, and how is that even relevant? Seems like a weird straw man argument or something. The potential risks of this is blown way out of proportions. You're still in control over the domain, just not the zone. Do stupid things, win stupid prices? In this case, letting someone else control your zone because you failed to understand how DNS works.