mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #3125] Recursor: queries for NS RRset return empty results #1138
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#1138
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 @divergentdave on GitHub (Jul 16, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3125
I noticed that the recursor returns an empty RRset when queried for NS records. This only happens when DNSSEC validation is disabled. To reproduce, run the
exploreexample, and then rundig @172.19.0.6 +rec NS testing.in the client container. The problem goes away when passing--dnssecto the example. This is probably happening because we are reusing a cached referral response instead of querying for the authoritative NS RRset, and enabling DNSSEC validation probably fixes it because the referral response lacks signatures, triggering another query. I suspect this is a regression following one of my recent recursor changes.@divergentdave commented on GitHub (Jul 17, 2025):
I confirmed that this regressed in PR #3043. This is related to #3008.