Route53 used as sceondary DNS server

Question

A customer wants to use Route 53 as Secondary DNS server to their on-premise Primary DNS server? And also, if there is some update on primary, it need to be automatically sync to secondary. Is it possible?

The customer told me that other competitors can do them all with good performance.

Thanks!

The customer told me that other competitors can do them all with good performance.

Thanks!

Accepted Answer

There is no out of the box option to make Route 53 a secondary DNS. Your customer could use something like Lambda function to read from primary from time to time, and update Route 53.

Something similar to this (although this article covers Private and not Public zones) : https://aws.amazon.com/blogs/compute/powering-secondary-dns-in-a-vpc-using-aws-lambda-and-amazon-route-53-private-hosted-zones/

Answer

We are looking for this as well. It's been 5 years since this questions was asked. 
Still not possible to use R53 as primary/secondary from my own master (or hidden master)?

Answer

Same question for me - to make Route 53 as secondary DNS align with the info from the Authoritative Nameserver I also need to update NS and SOA records, but R53 wouldn't let me!

Route53 used as sceondary DNS server

Conteúdo relevante