Ghost CNAMEs across AWS accounts usually mean the alias target is still owned by another distribution or a leftover hosted zone record, not a flaky DNS provider. Prefer an inventory that lists every CloudFront alias and Route53 alias for that hostname before you recreate anything, detach or delete the old distribution only after the alias is released, and wait for global DNS to drop the prior target before attaching the new one. Keep ACM certificates and alternate domain names on the same account boundary so a cross-account move cannot leave a half-attached name.
Ops prove-out after reclaiming the hostname: resolve the name from more than one public resolver and confirm it points only at the new distribution, then request the Host through the edge and read the served certificate SAN plus cache status. Watch CloudFront 4xx and alias conflict metrics for one deploy window — a lingering CNAMEAlreadyExists or wrong cert usually means another account still holds an alternate domain name. Keep a canary Host that never moved so you can tell a DNS propagation lag from a real ownership clash.