Sounds like cloudflare could add an atomic cname -> a record feature.
Cloudflare should support RFC 2136 which includes atomic updates and is the standard for DNS updates.
Honestly, I think this solution worked better than any dedicated feature could have, since it used the exact same existing codepaths that Cloudflare already had for CNAME flattening. Using CNAME records for self-documentation seems like a better practice anyway. Spending the time building a complicated new feature for such a rare case seems like a bad idea.
Re:Issues with upstream DNS provider
by exitnode_ttl0 on Tuesday August 23, 2022 @08:58PM
(#32573729)
Good points, thanks!
In our case, we have substantial logic running on the edge in Cloudflare Workers, as well as lots of other Cloudflare configuration options, and I don't even want to know what it could potentially do to our zone to remove the root DNS record that everything's tied to.