Add CAA records when creating A records for CDNs

[mikeshultz]

Some user's domains may need CAA records set for the CNAME target (e.g. shop.ogn.app) to allow GCP (and probably AWS) to issue certs for their CDN configuration.

Problem is, we can not add CAA records on a CNAME. Before the CDN records are built, shop.ogn.app would be a CNAME to the backend dshop.originprotocol.com. So, until that record is destroyed and the new A record is created for the CDN, the CAA records cannot be added.

So even though this is an edge case, it would be better taken care of in the respective DNS modules.

Labeling this a P3 because while this has shown up once, it's a pretty extreme edge case for our configuration. Maybe get to this next time someone is mucking around in DNS/CDN code.

[phyninja]

@mikeshultz I understood that with DNS, we cannot create a CAA record with same name as in a CNAME record. You're saying that if a shop admin first creates an CNAME record for their domain, and then decides to use a CDN with a CAA record attached, they would have to be considerate of something. Could you expand on what the issue here is?