[GH-ISSUE #2389] DNSSEC false positives #976

Closed
opened 2026-03-16 01:08:49 +03:00 by kerem · 2 comments
Owner

Originally created by @japaric on GitHub (Aug 27, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2389

Describe the bug
These are scenarios where hickory-dns sets the AD flag in the response when it ought not

To Reproduce
Send queries of the form A $SUB.extended-dns-errors.com. to hickory where $SUB is one of these

  • bad-ksk
  • bad-rrsig-dnskey
  • bad-rrsig-ksk
  • ds-bad-key-algo
  • ds-bad-tag
  • ds-bogus-digest-value
  • ds-reserved-key-algo
  • ds-unassigned-key-algo
  • no-dnskey-257
  • no-ds
  • no-ksk
  • no-rrsig-dnskey
  • no-rrsig-ksk

Expected behavior

In the case of these subdomains ds-reserved-key-algo, ds-unassigned-key-algo, no-ds, unbound responds with NOERROR and the AD flag unset. In the other cases, unbound responds with SERVFAIL.

hickory should behave similarly and definitively should not set the AD flag in the response.

System:

  • OS: Ubuntu
  • Architecture: x86_64
  • Version 24.04
  • rustc version: 1.80.1

Version:
Crate: hickory-dns
Version: 77bd54e2ca

Additional context
Results produced using the test suite that's being added in #2385

Originally created by @japaric on GitHub (Aug 27, 2024). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2389 **Describe the bug** These are scenarios where hickory-dns sets the AD flag in the response when it ought not **To Reproduce** Send queries of the form `A $SUB.extended-dns-errors.com.` to hickory where `$SUB` is one of these - [x] bad-ksk - [x] bad-rrsig-dnskey - [x] bad-rrsig-ksk - [x] ds-bad-key-algo - [x] ds-bad-tag - [x] ds-bogus-digest-value - [x] ds-reserved-key-algo - [x] ds-unassigned-key-algo - [x] no-dnskey-257 - ~~no-ds~~ - [x] no-ksk - [x] no-rrsig-dnskey - [x] no-rrsig-ksk **Expected behavior** In the case of these subdomains `ds-reserved-key-algo`, `ds-unassigned-key-algo`, `no-ds`, unbound responds with NOERROR and the AD flag unset. In the other cases, unbound responds with SERVFAIL. hickory should behave similarly and definitively should not set the AD flag in the response. **System:** - OS: Ubuntu - Architecture: x86_64 - Version 24.04 - rustc version: 1.80.1 **Version:** Crate: `hickory-dns` Version: 77bd54e2ca98973b40210f20772d5f7f2de18143 **Additional context** Results produced using the test suite that's being added in #2385
kerem 2026-03-16 01:08:49 +03:00
Author
Owner

@djc commented on GitHub (Sep 3, 2024):

Still two checkboxes left, should this be kept open for now?

<!-- gh-comment-id:2326282970 --> @djc commented on GitHub (Sep 3, 2024): Still two checkboxes left, should this be kept open for now?
Author
Owner
<!-- gh-comment-id:2326300684 --> @japaric commented on GitHub (Sep 3, 2024): no, those last two were fixed in #2399 : https://github.com/hickory-dns/hickory-dns/pull/2399/files#diff-59514c0e8f8e69369efb4c2ce32d3f0b9a9a5ba2db81351215b8c8971644ce56
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#976
No description provided.