trust-dns 0.18.0-alpha.2

Trust-DNS is a safe and secure DNS server with DNSec support. Eventually this could be a replacement for BIND9. The DNSSec support allows for live signing of all records, in it does not currently support records signed offline. The server supports dynamic DNS with SIG0 authenticated requests. Trust-DNS is based on the Tokio and Futures libraries, which means it should be easily integrated into other software that also use those libraries.
trust-dns-0.18.0-alpha.2 is not a library.

Overview

Trust-DNS provides a binary for hosting or forwarding DNS zones.

This a named implementation for DNS zone hosting. It is capable of performing signing all records in the zone for server DNSSec RRSIG records associated with all records in a zone. There is also a named binary that can be generated from the library with cargo install trust-dns. Dynamic updates are supported via SIG0 (an mTLS authentication method is under development).

Features

  • Dynamic Update with sqlite journaling backend (SIG0)
  • DNSSEC online signing (NSEC not NSEC3)
  • DNS over TLS (DoT)
  • DNS over HTTPS (DoH)
  • Forwarding stub resolver
  • ANAME resolution, for zone mapping aliass to A and AAAA records
  • Additionals section generation for aliasing record types

Future goals

  • Distributed dynamic DNS updates, with consensus
  • mTLS based authorization for Dynamic Updates
  • Online NSEC creation for queries
  • Full hint based resolving
  • Maybe NSEC3 and/or NSEC5 support

Minimum Rust Version

The current minimum rustc version for this project is 1.39

Versioning

Trust-DNS does it's best job to follow semver. Trust-DNS will be promoted to 1.0 upon stabilization of the publicly exposed APIs. This does not mean that Trust-DNS will necessarily break on upgrades between 0.x updates. Whenever possible, old APIs will be deprecated with notes on what replaced those deprecations. Trust-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.