Customer-owned zones preserve control over a customer's mail identity; platform-owned zones give the application a place where it can automate changes directly. TL;DR: commit the tenant reservation and a durable provisioning intent together, then reconcile DNS outside the signup transaction. Treat CNAME upsert and rollback as recoverable operations, and track SPF, DKIM, and DMARC separately before declaring the mail setup ready.
For a hypothetical B2B SaaS signup, I would put cedar.app.example in a platform-owned zone while the customer keeps customer.example and its mail policy. Suppose the CNAME write times out after the signup has committed. My first postmortem question would be: what page fired? A failed request counter does not establish whether the record exists, and a green signup dashboard does not establish that the customer's mail authenticates.…