DNS not resolving after 5 days on Previously Expired Domain

Question

I have a domain that went a couple of days past expiration and I was able to get logged in and renew it.  Because the domain was past expiration my hosted zone was removed.  I created a new one and set the NS records in the hosted zone to match what is in the domain name.  I created a www and root domain A record and after five days neither of them are working.  I do the internal tests and they come back ok.  But when I try to do a nslookup or ping on the name it wont resolve.  What can I do to help try and get my DNS entries to resolve again like they use to?  
  
Domain : ibbq4u.com  
  
Edited by: KevinMarkwardt on Jul 23, 2019 6:21 AM

Accepted Answer

Hi,  
  
You had the right idea, but you went the wrong direction. Name servers in the NS record for the hosted zone and for the domain registration are supposed to match, but they're supposed to match the name servers that Route 53 assigned to the hosted zone. The name servers that Route 53 assigned to the hosted zone typically should be the same as the name servers in the NS record, but they can be different.  
  
Here's how you fix that:  
1. Get the name servers that Route 53 assigned to the 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 NS record to use the name servers that you got in step 2. See "Editing Records":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-editing.html  
  
3. Update the name servers for the domain registration. 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

DNS not resolving after 5 days on Previously Expired Domain

関連するコンテンツ