mirror of
https://github.com/tuxis-ie/nsedit.git
synced 2026-04-26 16:15:54 +03:00
[GH-ISSUE #124] Add Batch Mode #73
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
pull-request
question
question
upstream
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsedit#73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bjoe2k4 on GitHub (Sep 26, 2016).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/124
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.
@tuxis-ie commented on GitHub (Sep 29, 2016):
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.