aws-samples / aws-samples/aws-lambda-mirror-dns-function
Zones with more than 100 records not handled
- Vorherrschende Sprache
- Python
- Sterne
- 41
- Forks
- 29
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
my source zone has approx 300 records in it.
on the first run all the records were created in route53.
on the next run however some records were attempted to be created again
> Transferring zone example.com from server 1.2.3.4
> Getting VPC SOA serial from Route 53
> Comparing SOA serial 2017091200 with 2017091200
> Updating as CREATE for A record test TTL 300 in zone example.com with []
> An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: Tried to create resource record set [name='test.example.com.', type='A'] but it already exists
> ERROR: Unable to update zone example.com
it appears that the software does not account for the fact that ListResourceRecords by default returns 100 records at a time.
see: http://docs.aws.amazon.com/Route53/latest/APIReference/API_ListResourceRecordSets.html
since only 100 records are fetched from route53, then remaining records are assumed missing and scheduled for creation. when the create is attempted it fails because the record already exists.
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.