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
After n edits of a master zone, there will be in the worst case n NOTIFY+AXFR actions, which i think is bad (or not really necessary), especially for large zones.
I was just wondering if there is a way to do multiple changes to a zone via nsedit and only increment the SOA at the end? I am thinking of some kind of batch mode, which can be turned on by a button for example, that temporarily disables soa-edit-api for the zone. After editing is finished, use the same button again to trigger/commit a SOA update and/or restore soa-edit-api.
The text was updated successfully, but these errors were encountered:
It would be possible, but would include keeping state of a zone in nsedit. The whole idea of nsedit is KISS, so don't do anything smart, just ask pdns.
The serial is overrated in pdns-context anyways, so it doesn't really matter.
After n edits of a master zone, there will be in the worst case n NOTIFY+AXFR actions, which i think is bad (or not really necessary), especially for large zones.
I was just wondering if there is a way to do multiple changes to a zone via nsedit and only increment the SOA at the end? I am thinking of some kind of batch mode, which can be turned on by a button for example, that temporarily disables soa-edit-api for the zone. After editing is finished, use the same button again to trigger/commit a SOA update and/or restore soa-edit-api.
The text was updated successfully, but these errors were encountered: