You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that all code that adds (or modifies) zonedata and then (for signed zones) also resigns parts should be restructured. Right now we add zone data in lots of places: adding KEY, adding CSYNC, adding CDS, adding DNSKEY, modifying SOA, adding DSYNC, adding DSYNC targets, etc, etc. Lots of locking and unlocking of the zonedata struct.
If we instead just created the RRset that should be added and then sent it to the DbUpdater() for publication and perhaps signing. Then the code in the sending end would be cleaned up and also the publication decision would be in a single place. For the agent case where we don't publish, there's a single place that can store away the RRset to be used to inform the operator that stuff needs publication.
No description provided.
The text was updated successfully, but these errors were encountered: