[Pdns-users] After upgrade from 4.0.x to 4.1.3, rrset deletions through API must come before replacements
jordan at webnames.ca
Thu Jul 19 18:42:39 UTC 2018
This might be too long to post here, so I thought I'd link to my Stack Overflow question, which hasn't gotten much attention: https://stackoverflow.com/questions/51295253/after-powerdns-upgrade-from-4-0-x-to-4-1-x-rrset-deletions-through-api-must-com.
Brief summary: After upgrading from version 4.0.x to 4.1.3 of the authoritative name server, it seems that the API requires us to send rrset deletions before replacements when there is a conflicting record. For example, if you have a CNAME on www.example.com <http://www.example.com> , and you want to delete that and put an A record there instead, you have to pass the DELETE rrsets before the REPLACE rrsets in the PATCH. Previously you could pass the DELETE rrsets at the end of the PATCH body, and the server would not throw an error.
I didn't see this called out in the documentation, and it's a fairly big breaking change for our use case. It would make sense to me for the API to process the DELETE rrsets first to avoid such collisions. Maybe this is related to one or both of these two items from https://doc.powerdns.com/authoritative/changelog/4.1.html#change-4.1.0-rc1:
* Forbid mixing CNAMEs and other RRSets in the API (Christan Hofstaedtler).
* References: #5305, pull request 5389
* Prevent duplicate records in single RRset (Christian Hofstaedtler).
* References: pull request 4195
So I guess my question is: Is this intended behavior? Is it documented anywhere else that I missed? Should I submit a bug on this, or is my workaround just common sense that everyone should implement?
Software Development Manager
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pdns-users