NS and SOA records in my host zone but can't find them when I use dig

Question

My domain is chopdev.co and I have created a public host zone.  
  
The NS records are:  
ns-1146.awsdns-15.org.   
ns-2019.awsdns-60.co.uk.   
ns-870.awsdns-44.net.   
ns-48.awsdns-06.com.  
  
The SOA record is (I changed to 1 second to see if it refresh faster):  
ns-1146.awsdns-15.org. awsdns-hostmaster.amazon.com. 1 1 1 1 1  
  
I tried both dig and nslookup and I am not see any of these records and all I see is SERVFAIL.  
  
Is there anything else I can do?  
  
Edited by: Blkc on Feb 5, 2019 1:37 PM

Answer

Hi,  
  
The name servers that Route 53 assigned to your hosted zone don't match the name servers for your domain. I'd guess that you deleted the hosted zone that Route 53 created when you registered the domain and later created a new hosted zone. When you create the new hosted zone, Route 53 assigned four new name servers to the hosted zone. However, Route 53 doesn't update the domain to use the four new name servers.  
  
Here's how you resolve the problem:  
1. Get the name servers for your hosted zone. 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 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

Answer

Thank you! Didn't know domain also has name servers.

NS and SOA records in my host zone but can't find them when I use dig

Contenuto pertinente