Domain migrated from old AWS to new AWS account - name server mismatch

The issue you're experiencing is due to a mismatch between the nameservers listed in your new Route 53 hosted zone and the nameservers registered for your domain. This mismatch is preventing proper DNS resolution for your domain.

When you transfer a domain between AWS accounts or create a new hosted zone, the nameservers assigned to the hosted zone are typically different from the previous ones. However, the domain's registration details (including the nameservers) don't automatically update to match the new hosted zone.

To resolve this issue, you need to update the nameservers at the domain registration level to match those of your new hosted zone. Here's what you should do:

1. In your new AWS account, go to the Route 53 console.

2. Navigate to "Registered Domains" and select your domain (thebluemarble.io).

3. Choose "Edit name servers" from the Actions menu.

4. Update the nameservers to match those listed in your new hosted zone:

   ns-1247.awsdns-27.org. ns-614.awsdns-12.net. ns-424.awsdns-53.com. ns-1730.awsdns-24.co.uk.

5. Save the changes.

After making these updates, it may take up to 48 hours for the changes to propagate globally. During this time, you might experience intermittent DNS resolution issues.

It's important to note that simply updating the nameservers in the hosted zone itself is not sufficient. The crucial step is updating the nameservers at the domain registration level to ensure that DNS queries are directed to the correct nameservers.

If you continue to experience issues after 48 hours, or if you're unable to update the nameservers as described above, you may need to contact AWS support for further assistance.
Sources
NS records not matching domain lookup | AWS re:Post
Replacing the hosted zone for a domain that is registered with Route 53 - Amazon Route 53
I changed DNS settings, but they haven't taken effect - Amazon Route 53