Zones with more than 100 records not handled
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- aws, python
- Domain
- cloud, networking
Research direction
Start by reading the Route 53 ListResourceRecords pagination behavior, then trace the Python transfer logic that compares fetched records with the source zone. Exercise the transfer with a zone containing more than 100 records; done means all records are considered before comparison and a subsequent run does not attempt duplicate creates.
Written by the indexing model from the issue text.
Description
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 [<DNS IN A rdata: 2.3.4.5>]
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.
- Dominant language
- Python
- Stars
- 41
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws-samples/aws-lambda-mirror-dns-function
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
aws-samples/aws-lambda-mirror-dns-function#8 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
aws-samples/aws-lambda-mirror-dns-function#2 · 1 comment ·
All issues in aws-samples/aws-lambda-mirror-dns-function
Similar issues
-
New InternshipOpennew_internship
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
[BUG] Reports tab: "Unban" button tooltip shows raw `{{ip}}` placeholder instead of the IP addressOpenbug javascript ui
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bunkerity/bunkerweb#4001 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
adobe-fonts/source-serif#153 ·