Skip to content

Emit EDE 33 (Negative Trust Anchor) when NTA is in effect - #1470

Open
farrokhi wants to merge 1 commit into
NLnetLabs:masterfrom
farrokhi:master
Open

Emit EDE 33 (Negative Trust Anchor) when NTA is in effect#1470
farrokhi wants to merge 1 commit into
NLnetLabs:masterfrom
farrokhi:master

Conversation

@farrokhi

Copy link
Copy Markdown

This implements responding with EDE 33 (Negative Trust Anchor) when the resolver returns an answer covered by an NTA. The behavior is specified in draft-farrokhi-dnsop-ede-nta and IANA has allocated EDE 33 for this purpose.

Affected responses are those whose names fall under a domain-insecure or insecure-lan-zones entry, or under an NTA added at runtime through unbound-control insecure_add, forward_add +i, or stub_add +i. The signal let clients know that an operator-driven validation bypass is in effect.

This covers responses that are covered by a `domain-insecure` or an
`insecure-lan-zones` entry, or during runtime using `unbound-control`
relevant subcommands. The idea is for the client to know this is an
operator-driven action to disabled validation on a given name.

This implements draft-farrokhi-dnsop-ede-nta
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

Successfully merging this pull request may close these issues.

1 participant