mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-24 18:55:55 +03:00
[GH-ISSUE #872] Not all records are returned from the additional section when making an SRV query #552
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#552
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 @rjloura on GitHub (Sep 23, 2019).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/872
Describe the bug
Made an SRV query which should return 12 SRV records in the answer section and 3 IN A records in the additional section. All 12 SRV records are returned but only the first (?) record from the additional section is returned.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected to see all 3
IN Arecords from the additional section. (See below fordigoutput)System:
Version:
Crate: resolver
Version: 0.12
Additional context
@bluejekyll commented on GitHub (Sep 23, 2019):
Hm, it's possible that there is a bug/feature in the SRV lookup logic. We might only be resolving the first SRV record fully? Given that this is just a filter on the IPs: https://github.com/bluejekyll/trust-dns/blob/master/crates/resolver/src/lookup.rs#L323
It probably means that not all the IPs were added to the Lookup. I'm pretty sure the logic for resolving the SRV record happens here: https://github.com/bluejekyll/trust-dns/blob/master/crates/resolver/src/lookup_state.rs#L205-L314
It might be that it's not following all the targets from all the SRV records returned?
@bluejekyll commented on GitHub (Sep 23, 2019):
More specifically, this might be the problem area: https://github.com/bluejekyll/trust-dns/blob/master/crates/resolver/src/lookup_state.rs#L261-L291
We might be filtering a little too aggressively. The trust-dns-resolver tries to put an easy to use API around this stuff, and I think that in the case of CNAME/SRV it might only follow that to a single record? I'll need to review this in more detail later, but we probably need make it more accepting of additional records, where it might currently be limiting the additionals returned.
@davepacheco commented on GitHub (Mar 2, 2022):
Thanks for the details. I just ran into the same issue.