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

Definition of positive or negative DNSSEC responses in the context of authoritative DNS #411

Open
cstrotm opened this issue Nov 20, 2022 · 2 comments

Comments

@cstrotm
Copy link

cstrotm commented Nov 20, 2022

The chapter #authoritative-behavior reads:

If the zone is signed, the server SHOULD also include positive or negative DNSSEC responses for these records in the Additional section.

I'm unsure what a positive or negative DNSSEC response might be from an authoritative DNS server.

I can imagine an authoritative DNS returning signatures (RRSIG) records for the records in the Additional section (standard DNSSEC behavior). However an authoritative DNS server does not do DNSSEC validation, so to my knowledge there is no "positive" or "negative" DNSSEC response possible.

@fl1ger
Copy link

fl1ger commented Nov 25, 2022

It means that if there are "positive" answers (SVCB exists) that the additional records (A/AAAA) should also include signatures (RRSIG) as you say. I assume the text means (or at least how I interpret it) that in case of an non existing A/AAAA record that the (NOERROR/NoData) DNSSEC prove for those should be added, which would require the NSEC(3) record with a bitmap plus the signature that does not have the missing address record, but I don't think any authoritative server does that when they include an existing record for the target name. It would be no harm as the additional section gets ignored most of the time anyway, but it is different from what authoritative servers do today AFAIK. I seem to recall that text being "appropriate DNSSEC records", maybe we should revert to that. As said most resolvers will ignore the additional section and query A/AAAA independent.

@bemasc
Copy link
Collaborator

bemasc commented Jul 26, 2023

It sounds like we could choose terms to make this a bit clearer.

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

No branches or pull requests

3 participants