Unable to synchronize DNS zones with Amazon Route 53: Tried to create resource record set but it already exists

Follow

Comments

4 comments

  • Avatar
    Dr. Koontz

    The only "workaround" I have found for this is to delete enough records for the hosted zone of example.com from Amazon Route 53 so there are less than 100 records. After doing that, and performing another sync, all of the records for the domain example.com will be properly populated back to Amazon Route 53.

    However, after a successful sync, subsequent synchronization attempts will once again result in the same error unless the above workaround is performed. So if there are required changes to the zone then following the above workaround will allow it to update all zone information successfully.

  • Avatar
    Ivan Postnikov

    @Dr. Koontz

    Hello!

    Indeed, currently, there is no workaround for 100+ records. 

    Synchronization for a smaller amount of records works as expected. 

  • Avatar
    Dr. Koontz

    Yes, but my point being is that if you have 100+ records, say for example 150 records, following what I posted above, ie deleting enough records from Amazon Route 53 to get the number below 100 (example: 98 or 99 records), then, when another sync is done, it will re-add all 150 records for the zone.

    So in this way it is a "workaround" because manually deleting the records to get them below 100 allows the extension to re-add all the records for the zone even if the number of records is above 100.

    The problem is that the extension is not yet capable of comparing more than 100 records at a time to see if an update for the records is required. The reason my workaround works is because no comparison is done to see if an update is necessary, the records are simply re-added to the zone.

  • Avatar
    Ivan Postnikov

    @Dr. Koontz

    Thank you for the clarification.
    The article will be updated.

Please sign in to leave a comment.

Have more questions? Submit a request