38 breaking releases

0.39.0 Feb 24, 2023
0.38.0 Nov 25, 2022
0.37.0 Oct 14, 2022
0.34.0 Jul 5, 2022
0.6.0 Mar 29, 2019

#2140 in Network programming

Download history 28913/week @ 2022-11-29 29946/week @ 2022-12-06 27954/week @ 2022-12-13 22753/week @ 2022-12-20 16807/week @ 2022-12-27 26364/week @ 2023-01-03 28816/week @ 2023-01-10 27984/week @ 2023-01-17 26457/week @ 2023-01-24 25224/week @ 2023-01-31 22861/week @ 2023-02-07 24605/week @ 2023-02-14 26084/week @ 2023-02-21 25050/week @ 2023-02-28 24609/week @ 2023-03-07 22435/week @ 2023-03-14

102,061 downloads per month
Used in 101 crates (3 directly)

MIT license


DNS name resolution

[Transport] for libp2p.

This crate provides the type [GenDnsConfig] with its instantiations [DnsConfig] and TokioDnsConfig for use with async-std and tokio, respectively.

A [GenDnsConfig] is an address-rewriting [Transport] wrapper around an inner Transport. The composed transport behaves like the inner transport, except that [Transport::dial] resolves /dns/..., /dns4/..., /dns6/... and /dnsaddr/... components of the given Multiaddr through a DNS, replacing them with the resolved protocols (typically TCP/IP).

The async-std feature and hence the DnsConfig are enabled by default. Tokio users can furthermore opt-in to the tokio-dns-over-rustls and tokio-dns-over-https-rustls features. For more information about these features, please refer to the documentation of trust-dns-resolver.

On Unix systems, if no custom configuration is given, trust-dns-resolver will try to parse the /etc/resolv.conf file. This approach comes with a few caveats to be aware of:

  1. This fails (panics even!) if /etc/resolv.conf does not exist. This is the case on all versions of Android.
  2. DNS configuration is only evaluated during startup. Runtime changes are thus ignored.
  3. DNS resolution is obviously done in process and consequently not using any system APIs (like libc's gethostbyname). Again this is problematic on platforms like Android, where there's a lot of complexity hidden behind the system APIs. If the implementation requires different characteristics, one should consider providing their own implementation of [GenDnsConfig] or use platform specific APIs to extract the host's DNS configuration (if possible) and provide a custom [ResolverConfig].


~357K SLoC