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

EDE (RFC8914) has no effect on unboundtest #18

Open
minfrin opened this issue Nov 9, 2024 · 0 comments
Open

EDE (RFC8914) has no effect on unboundtest #18

minfrin opened this issue Nov 9, 2024 · 0 comments

Comments

@minfrin
Copy link

minfrin commented Nov 9, 2024

While trying to get to the bottom of why unbound isn't giving any diagnostics for failed DNSSEC requests, I was led to unboundtest which wraps unbound.

Support for EDE in unboundtest was announced at https://community.letsencrypt.org/t/unboundtest-com-serving-more-informative-dnssec-error-logs/198380 but there doesn't appear to be evidence that it does anything.

An attempt to validate dnssec-failed.org doesn't contain the strings "EDE", "validation failure" or "bogus". The only indication that validation failed is the missing ad flag.

I am trying to work out if this is an unbound bug (the unbound people appear to be unaware that anything is broken), or a Redhat bug (Redhat has removed SHA1 from the OS, not sure if they broke anything in the process), or something else.

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