mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[GH-ISSUE #3053] Recursor may follow multiple CNAMEs with the same record name #1121
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#1121
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 (Jun 13, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3053
A CNAME record is supposed to be the only record stored at its name, but it is possible for noncompliant servers to return CNAME RRsets containing multiple records. Currently,
RecursorDnsHandle::resolve_cnames()will follow each in turn, combining their answers together. We should instead either pick one CNAME to follow, or return an error.The end-to-end test
recursor::cname::scenarios::cname_lookup_limit_testprovides an extreme example -- the dnslib server in that test returns 40 CNAMEs in most responses, providing an exponential number of CNAME chains of length 10. This test exercises theMAX_CNAME_LOOKUPSlimit. In fact, with default configuration, theMAX_CNAME_LOOKUPSerror can only be hit before therecursion_limiterror if some CNAME RRsets have more than one record.