
* update all READMEs with notices about the name change * update changelog for 0.24 * bump crate versions to 0.24 * update version notice information * update readmes to back reference trust-dns * rename all crates to hickory counterparts * replace all Trust-DNS references in code and comments with Hickory DNS * rename all Trust-DNS references to Hickory DNS in non-code * rename all trust-dns-resolver references to hickory-resolver * rename all trust-dns-client references to hickory-client * rename all trust-dns-proto references to hickory-proto * rename all trust-dns-server references to hickory-server * rename all trust-dns-compatibility references to hickory-compatability * rename all trust-dns-integration references to hickory-integration * rename all trust-dns-util references to hickory-util * Update MIT licenses to reference Hickory DNS * update all trust-dns references to hickory-dns * update all bluejekyll github references to hickorydns org * Update name in Changelog * make sure hickory-dns logs during tests * add changelogs for recent main additions * fix references to trust-dns and hickory in architecture * update a few trust-dns references in READMEs * fixup some dangling trust_dns references * replace fka with formerly in change log * replace all hickoydns org references to hickory-dns * replace all http links with https * update logos * update hickorydns to hickory-dns for all other org references * fix Notices of Trust-DNS to Hickory in each Readme
65 lines
2.2 KiB
Rust
65 lines
2.2 KiB
Rust
#![recursion_limit = "128"]
|
|
|
|
//! This example shows how to create a resolver that uses the tokio multithreaded runtime. This is how
|
|
//! you might integrate the resolver into a more complex application.
|
|
|
|
fn main() {
|
|
use hickory_resolver::{name_server::TokioConnectionProvider, TokioAsyncResolver};
|
|
use tokio::runtime::Runtime;
|
|
|
|
tracing_subscriber::fmt::init();
|
|
|
|
// Set up the standard tokio runtime (multithreaded by default).
|
|
let runtime = Runtime::new().expect("Failed to create runtime");
|
|
|
|
let resolver = {
|
|
// To make this independent, if targeting macOS, BSD, Linux, or Windows, we can use the system's configuration:
|
|
#[cfg(any(unix, windows))]
|
|
{
|
|
// use the system resolver configuration
|
|
TokioAsyncResolver::from_system_conf(TokioConnectionProvider::default())
|
|
}
|
|
|
|
// For other operating systems, we can use one of the preconfigured definitions
|
|
#[cfg(not(any(unix, windows)))]
|
|
{
|
|
// Directly reference the config types
|
|
use hickory_resolver::config::{ResolverConfig, ResolverOpts};
|
|
|
|
// Get a new resolver with the google nameservers as the upstream recursive resolvers
|
|
AsyncResolver::new(
|
|
ResolverConfig::google(),
|
|
ResolverOpts::default(),
|
|
runtime.handle().clone(),
|
|
)
|
|
}
|
|
}
|
|
.expect("failed to create resolver");
|
|
|
|
// Create some futures representing name lookups.
|
|
let names = &["www.google.com", "www.reddit.com", "www.wikipedia.org"];
|
|
let mut futures = names
|
|
.iter()
|
|
.map(|name| (name, resolver.lookup_ip(*name)))
|
|
.collect::<Vec<_>>();
|
|
|
|
// Go through the list of resolution operations and wait for them to complete.
|
|
for (name, lookup) in futures.drain(..) {
|
|
let ips = runtime
|
|
.block_on(lookup)
|
|
.expect("Failed completing lookup future")
|
|
.iter()
|
|
.collect::<Vec<_>>();
|
|
println!("{name} resolved to {ips:?}");
|
|
}
|
|
|
|
// Drop the resolver, which means that the runtime will become idle.
|
|
drop(futures);
|
|
drop(resolver);
|
|
}
|
|
|
|
#[test]
|
|
fn test_multithreaded_runtime() {
|
|
main()
|
|
}
|