Overview
Hickory DNS Async-Std Resolver is a library which implements the DNS resolver using the Hickory DNS Resolver library.
This library contains implementations for IPv4 (A) and IPv6 (AAAA) resolution, more features are in the works. It is built on top of the async-std async-io project, this allows it to be integrated into other systems using the async-std and futures libraries. The Hickory DNS project contains other libraries for DNS: a client library for raw protocol usage, a server library for hosting zones, and variations on the TLS implementation over rustls and native-tls.
NOTICE This project was rebranded from Trust-DNS to Hickory DNS and has been moved to the https://github.com/hickory-dns/hickory-dns organization and repo, from 0.24
and onward.
Features
- Various IPv4 and IPv6 lookup strategies
/etc/resolv.conf
based configuration on Unix/Posix systems- NameServer pools with performance based priority usage
- Caching of query results
- NxDomain/NoData caching (negative caching)
- TBD (in tokio impl): DNSSEC validation
- Generic Record Type Lookup
- CNAME chain resolution
- experimental mDNS support (enable with
mdns
feature) - TBD (in tokio impl): DNS over TLS (utilizing
native-tls
,rustls
, andopenssl
;native-tls
orrustls
are recommended) - TBD (in tokio impl): DNS over HTTPS (currently only supports
rustls
)
Example
use *;
use *;
use ;
async
Minimum Rust Version
The current minimum rustc version for this project is 1.67
Versioning
Hickory DNS does its best job to follow semver. Hickory DNS will be promoted to 1.0 upon stabilization of the publicly exposed APIs. This does not mean that Hickory DNS will necessarily break on upgrades between 0.x updates. Whenever possible, old APIs will be deprecated with notes on what replaced those deprecations. Hickory DNS will make a best effort to never break software which depends on it due to API changes, though this can not be guaranteed. Deprecated interfaces will be maintained for at minimum one major release after that in which they were deprecated (where possible), with the exception of the upgrade to 1.0 where all deprecated interfaces will be planned to be removed.