3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
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)?
con risposta un anno fa
0
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!
con risposta un anno fa
-2
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/
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa