Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

AWS Route53: Get DNS record set creation time

I use Python SDK to delete DNS record sets in Route53. Due to Route53 API throttling, the deletion fails sometimes and the stale DNS record set is building up.

As the DNS record set approaches the 10,000 limit, I want to delete the record sets that were created last year because they are not needed any longer. But I am unable to find the record creation time either using AWS CLI or using Python SDK (Boto3). Is there a way to get the DNS record creation time in Route53 using CLI or SDK?

like image 687
helloV Avatar asked Aug 01 '17 14:08

helloV


People also ask

How long does Route 53 take to propagate A record?

Amazon Route 53 is designed to propagate updates you make to your DNS records to its world-wide network of authoritative DNS servers within 60 seconds under normal conditions. A change is successfully propagated world-wide when the API call returns an INSYNC status listing.

Does Route 53 have a default for the time to live TTL value?

The AWS documentation states: "If an alias record points to an AWS resource, you can't set the time to live (TTL); Route 53 uses the default TTL for the resource."

How long does Route 53 take to register a domain?

Using AWS Route 53, it takes only 10 minutes to get ready to serve web site on a specific domain name you want to use.

Why does it take between 24 to 48 hours for changes made to a hosted zone in Amazon Route 53 to reflect globally?

Why does it take between 24-48hrs for changes made to a hosted zone in Amazon Route53 to reflect globally? DNS resolvers around the world cna only reflect the changes in their cache after the Time to Live (TTL) has expired, it is 24hrs by default.


1 Answers

After analysing the root cause of the problem you are facing, I think it is not specifically related to python or boto3, but it is related to your algorithm and aws route 53 service behavior, you said:

I use Python SDK to delete DNS record sets in Route53. Due to Route53 API throttling, the deletion fails sometimes and the stale DNS record set is building up.

I would recommend you to use a SQS queue as intermediate to delete records from Route53 asynchronously, eventually using exponential backoff and dead letter queues to improve the reliability of your process if you think some deletion is broken by another reason and should be postponed.

like image 86
Alessandro Oliveira Avatar answered Sep 19 '22 11:09

Alessandro Oliveira