New CNAME records not resolving after AWS account transfer

Question

I recently moved my domain from one AWS account to another. The CNAME records that I had in my hosted zone before the transfer continue to work correctly but any new CNAME records that I create won't resolve. Examples-
#### Pre-transfer record: https://www.whatsmydns.net/#CNAME/ondemand.kinectperformance.com
#### Post-transfer record: https://www.whatsmydns.net/#CNAME/go.kinectperformance.com
The internal Test Record function thinks everything is setup correctly.
Might this have something to do with name servers needing an update after the transfer?
Quite befuddled.
Thanks!

Answer

As you alluded to, you will need to update the Name Servers in the Registered Domains section of Route 53 (in the new/destination account) to the Name Servers used in the creation of the Public Hosted Zone in that new account. The steps are:

1. Sign in to the AWS Management Console and open the Route 53 console at https://console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered Domains.
3. Choose the name of the domain that you want to configure to use another DNS service.
4. Choose Add/Edit Name Servers.
5. Change the names of the name servers to the name servers for the correct PHZ [steps to find these here](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html)
6. Choose Update.

It is likely the Name Servers configured for the domain are still configured as the old accounts' Public Hosted Zone. You can verify the change with 'whois' at the command line:

```
$ whois kinectperformance.com
.....
Name Server: ns-1096.awsdns-09.org
Name Server: ns-127.awsdns-15.com
Name Server: ns-1797.awsdns-32.co.uk
Name Server: ns-619.awsdns-13.net
```

New CNAME records not resolving after AWS account transfer

Pre-transfer record: https://www.whatsmydns.net/#CNAME/ondemand.kinectperformance.com

Post-transfer record: https://www.whatsmydns.net/#CNAME/go.kinectperformance.com

相關內容