Struct hickory_resolver::config::ResolverConfig

pub struct ResolverConfig { /* private fields */ }

Configuration for the upstream nameservers to use for resolution

Implementations

impl ResolverConfig

pub fn new() -> Self

Creates a new empty configuration

pub fn google() -> Self

Creates a default configuration, using 8.8.8.8, 8.8.4.4 and 2001:4860:4860::8888, 2001:4860:4860::8844 (thank you, Google).

Please see Google’s privacy statement for important information about what they track, many ISP’s track similar information in DNS. To use the system configuration see: Resolver::from_system_conf and AsyncResolver::from_system_conf

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn google_tls() -> Self

Available on crate feature dns-over-tls only.

Creates a default configuration, using 8.8.8.8, 8.8.4.4 and 2001:4860:4860::8888, 2001:4860:4860::8844 (thank you, Google). This limits the registered connections to just TLS lookups

Please see Google’s privacy statement for important information about what they track, many ISP’s track similar information in DNS. To use the system configuration see: Resolver::from_system_conf and AsyncResolver::from_system_conf

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn google_https() -> Self

Available on crate feature dns-over-https only.

Creates a default configuration, using 8.8.8.8, 8.8.4.4 and 2001:4860:4860::8888, 2001:4860:4860::8844 (thank you, Google). This limits the registered connections to just HTTPS lookups

Please see Google’s privacy statement for important information about what they track, many ISP’s track similar information in DNS. To use the system configuration see: Resolver::from_system_conf and AsyncResolver::from_system_conf

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn google_h3() -> Self

Available on crate feature dns-over-h3 only.

Creates a default configuration, using 8.8.8.8, 8.8.4.4 and 2001:4860:4860::8888, 2001:4860:4860::8844 (thank you, Google). This limits the registered connections to just HTTP/3 lookups

Please see Google’s privacy statement for important information about what they track, many ISP’s track similar information in DNS. To use the system configuration see: Resolver::from_system_conf and AsyncResolver::from_system_conf

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn cloudflare() -> Self

Creates a default configuration, using 1.1.1.1, 1.0.0.1 and 2606:4700:4700::1111, 2606:4700:4700::1001 (thank you, Cloudflare).

Please see: https://www.cloudflare.com/dns/

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn cloudflare_tls() -> Self

Available on crate feature dns-over-tls only.

Creates a configuration, using 1.1.1.1, 1.0.0.1 and 2606:4700:4700::1111, 2606:4700:4700::1001 (thank you, Cloudflare). This limits the registered connections to just TLS lookups

Please see: https://www.cloudflare.com/dns/

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn cloudflare_https() -> Self

Available on crate feature dns-over-https only.

Creates a configuration, using 1.1.1.1, 1.0.0.1 and 2606:4700:4700::1111, 2606:4700:4700::1001 (thank you, Cloudflare). This limits the registered connections to just HTTPS lookups

Please see: https://www.cloudflare.com/dns/

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn quad9() -> Self

Creates a configuration, using 9.9.9.9, 149.112.112.112 and 2620:fe::fe, 2620:fe::fe:9, the “secure” variants of the quad9 settings (thank you, Quad9).

Please see: https://www.quad9.net/faq/

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn quad9_tls() -> Self

Available on crate feature dns-over-tls only.

Creates a configuration, using 9.9.9.9, 149.112.112.112 and 2620:fe::fe, 2620:fe::fe:9, the “secure” variants of the quad9 settings. This limits the registered connections to just TLS lookups

Please see: https://www.quad9.net/faq/

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn quad9_https() -> Self

Available on crate feature dns-over-https only.

Creates a configuration, using 9.9.9.9, 149.112.112.112 and 2620:fe::fe, 2620:fe::fe:9, the “secure” variants of the quad9 settings. This limits the registered connections to just HTTPS lookups

Please see: https://www.quad9.net/faq/

NameServerConfigGroups can be combined to use a set of different providers, see NameServerConfigGroup and ResolverConfig::from_parts

pub fn from_parts<G: Into<NameServerConfigGroup>>( domain: Option<Name>, search: Vec<Name>, name_servers: G ) -> Self

Create a ResolverConfig with all parts specified

Arguments

• domain - domain of the entity querying results. If the Name being looked up is not an FQDN, then this is the first part appended to attempt a lookup. ndots in the ResolverOption does take precedence over this.
• search - additional search domains that are attempted if the Name is not found in domain, defaults to vec![]
• name_servers - set of name servers to use for lookups, defaults are Google: 8.8.8.8, 8.8.4.4 and 2001:4860:4860::8888, 2001:4860:4860::8844

pub fn domain(&self) -> Option<&Name>

Returns the local domain

By default any names will be appended to all non-fully-qualified-domain names, and searched for after any ndots rules

pub fn set_domain(&mut self, domain: Name)

Set the domain of the entity querying results.

pub fn search(&self) -> &[Name]

Returns the search domains

These will be queried after any local domain and then in the order of the set of search domains

pub fn add_search(&mut self, search: Name)

Add a search domain

pub fn add_name_server(&mut self, name_server: NameServerConfig)

Add the configuration for a name server

pub fn name_servers(&self) -> &[NameServerConfig]

Returns a reference to the name servers

pub fn client_config(&self) -> &Option<TlsClientConfig>

Available on crate feature dns-over-rustls only.

return the associated TlsClientConfig

pub fn set_tls_client_config(&mut self, client_config: Arc<ClientConfig>)

Available on crate feature dns-over-rustls only.

adds the rustls::ClientConf for every configured NameServer of the Resolver.

use std::sync::Arc;

use rustls::{ClientConfig, ProtocolVersion, RootCertStore, OwnedTrustAnchor};
use hickory_resolver::config::ResolverConfig;
use webpki_roots;

let mut root_store = RootCertStore::empty();
root_store.add_server_trust_anchors(webpki_roots::TLS_SERVER_ROOTS.iter().map(|ta| {
    OwnedTrustAnchor::from_subject_spki_name_constraints(
        ta.subject,
        ta.spki,
        ta.name_constraints,
    )
}));

let mut client_config = ClientConfig::builder()
    .with_safe_default_cipher_suites()
    .with_safe_default_kx_groups()
    .with_protocol_versions(&[&rustls::version::TLS12])
    .unwrap()
    .with_root_certificates(root_store)
    .with_no_client_auth();

let mut resolver_config = ResolverConfig::quad9_tls();
resolver_config.set_tls_client_config(Arc::new(client_config));

Trait Implementations

impl Clone for ResolverConfig

fn clone(&self) -> ResolverConfig

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ResolverConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for ResolverConfig

fn default() -> Self

Creates a default configuration, using 8.8.8.8, 8.8.4.4 and 2001:4860:4860::8888, 2001:4860:4860::8844 (thank you, Google).

Please see Google’s privacy statement for important information about what they track, many ISP’s track similar information in DNS. To use the system configuration see: Resolver::from_system_conf and AsyncResolver::from_system_conf

impl<'de> Deserialize<'de> for ResolverConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ResolverConfig

fn eq(&self, other: &ResolverConfig) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for ResolverConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl Eq for ResolverConfig

impl StructuralPartialEq for ResolverConfig