docs: Record not signing zones as a non-goal - #126
Open
ecv wants to merge 1 commit into
Open
Conversation
ecv
force-pushed
the
docs/dnssec-non-goal
branch
from
August 31, 2026 20:49
4704844 to
fa0d187
Compare
ecv
marked this pull request as ready for review
September 1, 2026 15:51
ecv
force-pushed
the
docs/dnssec-non-goal
branch
from
September 2, 2026 17:49
fa0d187 to
09e253f
Compare
The service does not sign the zones it is authoritative for, and that was written down nowhere. Anyone reading the architecture found silence where a decision should be, so it kept coming back as an open roadmap question, and a customer delegating a signed domain had no warning that they were about to break it. State the decision where the service's design lives, with the reasoning behind it and the conditions that would justify changing it. Key changes: - Add an architecture document covering why zones are unsigned: a signed zone fails closed and whole, key management and DS coordination sit with a registrar the service does not control, validation failures are invisible on the query path, and multi-provider serving stops being straightforward - Record what delegating an already-signed domain requires, and the ordering that avoids taking the domain dark - Name the condition that would reopen the decision, a customer or compliance requirement, which is a product question rather than an operational one - Surface the non-goal from the architecture overview so a reader meets it without going looking
ecv
force-pushed
the
docs/dnssec-non-goal
branch
from
September 3, 2026 15:17
09e253f to
10ae903
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Datum does not sign the zones it serves authoritatively, and nobody wrote that down, so reviewers kept reopening it as a roadmap question and a customer delegated an already-signed domain and took it dark for every validating resolver.
This records the decision where the service's design lives, with the reasoning, what delegating a signed domain requires, and the one condition that would justify changing course.
Nothing in the service changes, because signing was never implemented; the point is to say so on purpose rather than by omission.
Note
Stacked on #119, which is the base branch and owns the overview page this adds a section to, so merge that one first and this retargets on its own.
Test plan
Related to datum-cloud/enhancements#850