Transferred a domain from GoDaddy to Route 53 but the internet hasn't gotten the memo

When you transfer a domain from one registrar to another (like GoDaddy to Route 53), one of the most critical steps is ensuring that the nameservers are properly updated. Based on your description, it sounds like your domain transfer was completed, but the nameserver configuration might not have been properly updated.

Here's what's likely happening: Even though you've transferred the domain registration to AWS Route 53, your domain might still be using the old nameservers from GoDaddy or pointing to Heroku's DNS configuration. This would explain why your website continues to resolve to Heroku despite your efforts.

To resolve this issue:

1. Check your domain's nameservers in Route 53:

• Go to Route 53 console > Registered domains
• Find your domain (rileyshaw.com) and check the nameservers listed

2. Verify that these nameservers match the ones in your Route 53 hosted zone:

• Go to Route 53 console > Hosted zones
• Select your domain and check the NS records

3. If they don't match, update the nameservers for your domain:

• In the Route 53 console, go to your domain's details
• Choose "Edit name servers" from the Actions menu
• Update them to match your Route 53 hosted zone's nameservers

4. Ensure your Route 53 hosted zone has the correct records:

• For S3 website hosting, you need an A record alias pointing to your S3 website endpoint

This issue is often referred to as a "glue record" problem, where the domain registration is using different nameservers than intended. Even though GoDaddy no longer manages your domain, if the nameservers weren't properly updated during the transfer, DNS queries would still be directed according to the old configuration.

After making these changes, it may still take up to 48 hours for DNS changes to fully propagate worldwide, though it's often much faster. If you've verified all these settings and are still experiencing issues after 48 hours, it would be worth considering AWS Support options, as this appears to be a persistent technical issue that may require more detailed investigation.
Sources
I changed DNS settings, but they haven't taken effect - Amazon Route 53
Name Server has not correctly transferred from UK2 to AWS Route53 | AWS re:Post
Migrated Domain unable to resolve new records. | AWS re:Post