Hi,
Thanks for your message!
I’m not fully clear why your use case would require a modification to deSEC’s services, as opposed to modifying your daemon such that only one request is sent to deal with both updates. (This is how thousands of domains get updated.)
The main problem with allowing two separate update requests in quick succession is that people will almost inevitably run into some sort of race condition. (Of course, that doesn’t apply to your case, but experience shows that misconfigured clients will send 2 requests for IPv4 only, for example. In fact, this is the case today, and the second request is rejected for rate limiting – with your proposal, we’d have to deal with the implications of this concurrency.)
In any case, feel free to open a feature request issue on GitHub for this, so that we can track it there. If other people show thumbs up etc., we might consider doing this change.
Stay secure,
Peter