I can't confirm that your entire configuration is correct, but I did see that the NS record in the swiftthistle.co.uk hosted zone and the domain registration are both using the wrong name servers.
When you create a hosted zone, Route 53 assigns four name servers to that hosted zone. When you create another hosted zone, Route 53 assigns four different name servers to that hosted zone. Based on the current settings, I'd guess that you:
~ Deleted one hosted zone
~ Created another hosted zone
~ Changed the NS record in the new hosted zone to use the name servers from the domain registration, which has the name servers from the old hosted zone
Here's how you fix that:
- Get the name servers that Route 53 assigned to the new hosted zone. See "Getting the Name Servers for a Public Hosted Zone" in the Route 53 Developer Guide:
- Update the NS record in the new hosted zone to use the name servers that you got in step 1. See "Editing Records":
- Update the domain registration to use the name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":
On a related note, you might also want to take a peek at "Getting Started," which explains how to use Route 53, S3, and CloudFront to distribute your content:
There are several versions of that explanation floating around in various docs; this is my favorite. :-)
Thank you for you excellent and speedy answer! I think I did delete and remake the hosted zone at some point when I wasn't using the domain.
I'll assume this will work (Waiting on the name space change taking effect :) ) so I'll mark this as answered.
p.s. I think I saw your solution posted somewhere else but the instructions weren't clear, so thank you very much for making it understandable!
- AWS OFICIALAtualizada há 2 meses