mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[PR #2888] [MERGED] Recursor: refactor handling of glue records in ns_pool_for_zone() #3401
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#3401
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/2888
Author: @divergentdave
Created: 3/26/2025
Status: ✅ Merged
Merged: 3/29/2025
Merged by: @djc
Base:
main← Head:david/recursor-glue-refactor📝 Commits (6)
f6a913cFix variable namese64aed4Return response from RecursorDnsHandle::lookup()15e3181Simplify processing of glue addresses21deaf9Store glue records in a map285ea1eExtract add_glue_to_map()f01f7ceCollect glue IPs directly from the response📊 Changes
1 file changed (+77 additions, -50 deletions)
View changed files
📝
crates/recursor/src/recursor_dns_handle.rs(+77 -50)📄 Description
This PR refactors
RecursorDnsHandleto retrieve glue records directly from responses to NS queries, rather than solely relying onDnsLruto store the glue records, and return them to fetches using A/AAAA queries. This is a prerequisite to switching to atomically caching responses, as discussed in #2602.I tested this by deleting the
self.record_cache.get()calls, and confirming that conformance tests still pass.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.