Zone not propagating

Question

I've got a public hosted zone: open-sotw.net that I can't seem to make work. I bought the domain via AWS which automatically created everything - no luck getting a CNAME or A record to resolve, I've since destroyed and recreated the zone, but still nothing seems to become public.  I want to have a www.open-sotw.net website, and possibly static.open-sotw.net and api.open... etc, but nothing on this zone seems to propagate. I can't even see that the NS and SOA entries are being propagated publicly?  
  
Any suggestions?

Accepted Answer

Hi,  
  
Name servers appear in three places, and typically they should all be in synch:  
~ The name servers that Route 53 assigns to a hosted zone when you create it. These are the "master" name servers and can't be changed. Name servers in the other locations usually match these.  
~ The name servers in the NS record in the hosted zone.  
~ The name servers that are associated with the domain registration. These are the name servers that control which DNS configuration is in use.  
  
For open-sotw.net, the master name servers match the name servers in the NS record, but the name servers for the domain registration don't match the first two. That's because Route 53 assigns a new set of name servers whenever you create a new hosted zone, but it doesn't automatically update the name servers for the domain.  
  
Here's how you fix it:  
1. Get the name servers that Route 53 assigned to the hosted zone when you created it. See "Getting the Name Servers for a Public Hosted Zone" in the _Route 53 Developer Guide_:  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html  
  
2. Update the domain registration to use the four name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html  
  
Scott

Zone not propagating

Relevant content