mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #2284] add DNSSEC validation to the recursive resolver tool #955
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#955
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yonas on GitHub (Jul 4, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2284
Is your feature request related to a problem? Please describe.
It would be great if the recursive resolver tool (not the server) supported DNSSEC.
@bluejekyll commented on GitHub (Jul 5, 2024):
This work is in progress. It's targeted for delivering by year end.
@bluejekyll commented on GitHub (Jul 5, 2024):
see: #1718
@japaric commented on GitHub (Jul 10, 2024):
@bluejekyll I think yonas is specifically referring to adding DNSSEC validation support to the
recurse.it would not be too hard to conditionally set the DNSSEC policy here (
RecursorBuilder::dnssec_policy) and that should do the trick but I don't think this tool has much in the way of tests (+). OTOH, it's going to reuse theRecursorcode which is being tested by the conformance test suite so maybe that's fine.(+) in principle, it would be possible to set up a
dns-test-based test and do some snapshot testing of the tool's output