mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[GH-ISSUE #296] Feature Request: zone transfer and notification support #151
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#151
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 @HendrikF on GitHub (Feb 27, 2022).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/296
If acme-dns would support zone transfer it could be operated as a primary behind an existing name server. This means that you would not need a dedicated IP-address to operate acme-dns on.
Another possibility would be to operate it behind a signing-secondary to get DNSSEC for the acme-dns zone.
If this is implemented acme-dns should be able to notify configured secondaries to trigger an immediate zone transfer.