Second-level domain records moved to new HostedZone not recognized

Question

I had a HostedZone with records mapping a SLD (A and AAAA alias records) to a CloudFront distribution. In the process of migrating my infrastructure to CDK, I created a new HostedZone (same SLD) with records for multiple environments on sub-domains, including 2 (blue/green) for production. The SLD records point to the current active color. When everything was in place, I deleted the old HostedZone and pointed my domain provider (NameCheap) at the new NS records.

* All subdomains (blue, green, staging, sandbox, etc.) resolve and serve data correctly.
* A common certificate is used for all distros, and lists sld.com plus *.sld.com.
* The SLD still points to the old distribution, even though the records clearly show it should point to the same distro as green.
* There is nothing in AWS currently that should correlate the SLD with the old distro.
* When I deactivate the old distro, the site is unavailable; it does not fail over to the new site.
* The NS records are correct in my NameCheap account.
* Whois confirms the correct name servers are being used
* It has been a month since attempted cutover; no TTL issues should apply.

![Enter image description here](/media/postImages/original/IMhJHSIp5LR5e8SxvnEcjERw)
![Enter image description here](/media/postImages/original/IM_IsU1LhbTIaNMxC_dHp6ag)

BrianGray · Accepted Answer

Thank you, Malini, that was it!

The SLD was listed as an alternate host name not in blue, but in the old "prod" distro. So I guess when I deploy, I need to deploy with only the TLD in the CDK stack, then test for success and when changing the SLD A and AAAA records also manually remove the SLD from the old alternate name list and add it to the new one. Not quite zero downtime, but close enough. I appreciate the help!

Second-level domain records moved to new HostedZone not recognized

Relevant content