Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DS records enforce the use of a single DNSKEY RRset #2

Open
Philip-NLnetLabs opened this issue Jan 22, 2025 · 1 comment
Open

DS records enforce the use of a single DNSKEY RRset #2

Philip-NLnetLabs opened this issue Jan 22, 2025 · 1 comment

Comments

@Philip-NLnetLabs
Copy link
Member

Issue by Ben Schwartz:

DS records enforce the use of a single DNSKEY RRset (at the apex of
the zone).

I don't think this is true. I would agree that it requires all DNSKEY
RRsets to cover the same set of algorithms.

@Philip-NLnetLabs
Copy link
Member Author

Sent in reponse to mailing list:
That language can be more precise. DS records enforce that the DNSKEY RRset is
located at the apex of the zone. There is no way around that.

It is true that different authoritative servers may serve different versions
of the DNSKEY RRset provided that all keys that are used to signed the zone
(ZSK) are in all copies of the DNSKEY RRset. So in practice this does not
avoid the need to coordinate in a multi-signer setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant