mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[PR #2983] [MERGED] Make one more NS query to better align with RFC 9156 #3471
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#3471
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?
📋 Pull Request Information
Original PR: https://github.com/hickory-dns/hickory-dns/pull/2983
Author: @divergentdave
Created: 5/9/2025
Status: ✅ Merged
Merged: 5/19/2025
Merged by: @divergentdave
Base:
main← Head:david/qname-minimization-last-query📝 Commits (1)
75691d8Make one more NS query to better align w/ RFC 9156📊 Changes
4 files changed (+71 additions, -246 deletions)
View changed files
📝
conformance/packages/conformance-tests/src/resolver/dnssec/regression.rs(+18 -4)📝
crates/recursor/src/recursor_dns_handle.rs(+38 -234)📝
crates/server/src/store/recursor.rs(+2 -2)📝
tests/e2e-tests/src/recursor/delegation/scenarios.rs(+13 -6)📄 Description
This implements #2938, to better align with the QNAME minimization algorithm in RFC 9156. We now only send the original query once. This PR removes a significant amount of code that handled referral responses in the event that the QNAME is at a zone apex. I had to rework the name server topology in one ignored conformance test so that it still exercises the same incorrect caching behavior.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.