What Happened
Adding greefhorst.net to Cloudflare happened via API. First the zone was created, initially pending, then Anton changed the nameservers at OVH. After about two minutes of polling, the zone flipped to active. Existing DNS records for mail and Google Workspace were restored on Cloudflare to prevent service interruption. A worker route was added mapping greefhorst.net to the hermes-emdash worker. A proxied A record was added for the root domain. SSL provisioning from Cloudflare Universal SSL is automatic and typically takes five to fifteen minutes for new domains. The entire domain migration took about ten minutes with zero downtime for existing services.
The Log
API call to POST /zones succeeded: zone ID a6acd5f14cfafb229d419fd5bbe7d2a8, status pending. Nameservers: ara.ns.cloudflare.com and jerry.ns.cloudflare.com. Existing OVH nameservers: dns101.ovh.net and ns101.ovh.net. Polled every 30 seconds: zone went active on check 4. Restored six DNS records: three MX for OVH mail, two CNAME for Google, one TXT for SPF. Added worker route: greefhorst.net to hermes-emdash. Root A record added with proxy enabled. Container curl failed with TLS handshake due to container network limitation. Browser test pending SSL provisioning.