Skip to content

Latest commit

 

History

History
36 lines (23 loc) · 2.97 KB

ARCHITECTURE.md

File metadata and controls

36 lines (23 loc) · 2.97 KB
Raw

Architecture of Hickory DNS

The Hickory DNS libraries are built from the ground up to be asynchronous. This project grew from first using non-blocking IO interfaces (before Futures 0.1 or async/await had landed in Rust). There are some artifacts of this history sporadically left around the project. Please feel free to submit PRs that clean up areas that still have hand-written Futures based state-machines. Additionally, much of the project was written by @bluejekyll while he learned the Rust language–this means that there may be patterns or missing common implementations in places where he didn't know better. Feel free to clean that up if you feel open to submitting a PR.

Layout

Most of the project is in the form of crates. The crates are all individually published to crates.io.

The project has these high-level crates (to be used as dependencies in other projects):

  • hickory-resolver - implements a stub-resolver with support for CNAME chasing and other things, abstract over runtimes (Tokio supported by default)
  • async-std-resolver - an abstraction of hickory-resolver using the async-std runtime
  • hickory-client - a bare-bones client crate, most useful for dynamic DNS updates
  • hickory-server - implements support for hosted Authorities of various types
  • tokio-resolver - (under consideration, currently Tokio support is directly in hickory-resolver)

Low-level crates supporting the above high-level crates:

  • hickory-proto - the lowest level crate, implements the basics of DNS

Binaries:

  • hickory-dns - server binary, hickory-dns, for hosting authorities, zones, and/or setting up a forwarder
  • hickory-util - helpful utilities, e.g. resolve for a CLI resolver, as well as some DNSSEC utilities

Old and Outdated crates:

TBD

More on general patterns used in each library