mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #2762] timeout - while nslookup provides response #1057
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#1057
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 @efraimglobusM on GitHub (Feb 10, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2762
I am experiencing timeouts when performing an SRV record lookup using trust-dns-resolver. The same query works fine when using nslookup, which returns a non-authoritative response from my internal DNS server. However, trust-dns-resolver times out.
Expected Behavior
When running the following nslookup command:
nslookup -type=SRV _ldap._tcp.domain2.test.local
I get a non-authoritative answer:
Server: dc1.domain1.test.local
Address: daf::200
Non-authoritative answer:
_ldap._tcp.domain2.test.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = dc5.domain2.test.local
I expect trust-dns-resolver to return dc5.domain2.test.local as the SRV target.
Actual Behavior
When I run the following Rust code i get timeout
Does trust-dns-resolver reject non-authoritative responses by default?
Is there a way to force it to accept non-authoritative answers like nslookup does?
Are there any debugging options to inspect why the resolver hangs or times out?
@efraimglobusM commented on GitHub (Feb 10, 2025):
tokio_from_system_conf solved the issue