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

rec: Backport 9471 to rec-4.4.x: Log when going Bogus because of a missing SOA in authority #9528

Merged

Conversation

omoerbeek
Copy link
Member

A missing SOA in the authority section of negative (NXDOMAIN, NODATA)
answers in a DNSSEC-secure zone currently leads to a Bogus result,
because the needed NSEC/NSEC3 could not be validated.

(cherry picked from commit 832f4fb)

Backport of #9471

Short description

Checklist

I have:

  • read the CONTRIBUTING.md document
  • compiled this code
  • tested this code
  • included documentation (including possible behaviour changes)
  • documented the code
  • added or modified regression test(s)
  • added or modified unit test(s)
  • checked that this code was merged to master

A missing SOA in the authority section of negative (NXDOMAIN, NODATA)
answers in a DNSSEC-secure zone currently leads to a Bogus result,
because the needed NSEC/NSEC3 could not be validated.

(cherry picked from commit 832f4fb)
@omoerbeek omoerbeek added the rec label Sep 25, 2020
@omoerbeek omoerbeek added this to the rec-4.4.0 milestone Sep 25, 2020
@omoerbeek omoerbeek changed the title rec: Log when going Bogus because of a missing SOA in authority rec: Backport 9471 to rec-4.4.x: Log when going Bogus because of a missing SOA in authority Sep 25, 2020
@omoerbeek omoerbeek merged commit 735c219 into PowerDNS:rel/rec-4.4.x Sep 25, 2020
@omoerbeek omoerbeek deleted the backport-9471-to-rec-4.4.x branch September 25, 2020 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants