mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #2263] Are SRV/TXT lookup errors retried? #943
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#943
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 @isabelatkinson on GitHub (Jun 27, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2263
Hello! I work on the MongoDB Rust driver, and we are currently investigating whether we should retry SRV/TXT lookup when errors are encountered during client creation. We currently use
TokioAsyncResolverto perform these lookups. Are there any errors that may occur during lookup (i.e. insrv_lookupandtxt_lookup) that trigger an internal retry? We want to avoid double-retrying for errors that are already handled by the resolver.@djc commented on GitHub (Jun 28, 2024):
Have a look at the
RetryDnsHandleand the logic for trying a request against aNameServerPool?(There's also some logic in the
LookupFuture.)@isabelatkinson commented on GitHub (Jul 1, 2024):
Thanks!