mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #1004] Can't create custom ResolverOpts #589
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#589
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 @ackintosh on GitHub (Jan 31, 2020).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1004
I would like to create custom ResolverOpts which has
ip_strategy: LookupIpStrategy::Ipv6Onlyin order to query AAAA record but I got the compile error:(trust-dns-resolver 0.19.2)
Is there any way to create custom ResolverOpts?
@bluejekyll commented on GitHub (Jan 31, 2020):
This second construction of the Opts should work for you, is it not?:
Specify all the fields you want before the
..ResolverOpts::default()@ackintosh commented on GitHub (Jan 31, 2020):
Hmm... I got the same error with the second construction:
Is it due to
pub(crate)visibility?github.com/bluejekyll/trust-dns@2724575aaf/crates/resolver/src/config.rs (L644-L650)@bluejekyll commented on GitHub (Feb 1, 2020):
Huh, well we can make those public to make this easier. I think the motivation here was to not make options public that might create awkward issues. If you want to submit a PR for this, that would be great. As a work around, you can do this:
That should work without issue.
@ackintosh commented on GitHub (Feb 2, 2020):
I've confirmed that workaround works. Thanks!
I'll file a PR for this. :octocat: