crates/server/README.md
hickory-server is a library for integrating safe and secure DNS servers into
an async Tokio application. It supports a variety of protocol features
(DNSSEC, TSIG, SIG(0), DoT, DoQ, DoH). Servers can be operated in an authoritative
role, or as a forwarding resolver, stub resolver, or a recursive resolver
(experimental).
See the hickory-dns binary crate for a complete application built using
hickory-server.
Features requiring cryptography require selecting a specific cryptography provider. See the project README for more information.
The following DNS protocols are optionally supported:
In order to use these optional protocols you must enable a cargo feature corresponding to your desired cryptography provider:
tls-aws-lc-rs or tls-ring.https-aws-lc-rs or https-ringquic-aws-lc-rs or quic-ringh3-aws-lc-rs or h3-ringIn order to use DNSSEC you must enable a cargo feature corresponding to your desired cryptography provider:
dnssec-aws-lc-rsdnssec-ringThe current root key is bundled into the system, and used by default. This gives validation of DNSKEY and DS records back to the root. NSEC and NSEC3 are implemented.
resolver - support for DNS query resolving.recursor (experimental) - support for recursive resolution.sqlite - support maintaining zone data in a SQLite database. Required for dynamic DNS support.blocklist - support configuring allow/deny blocklists.toml - support for TOML configuration.metrics - support exposing metrics using the metrics crate.rustls-platform-verifier - use the system verifier for TLS with
rustls-platform-verifier.webpki-roots - use the webpki-roots crate for TLS certificate verification.