A Rust based DNS client and server, built to be safe and secure from the ground up.
- Build a safe and secure DNS server and client with modern features.
- No panics, all code is guarded
- Use only safe Rust, and avoid all panics with proper Error handling
- Use only stable Rust
- Protect against DDOS attacks (to a degree)
- Support options for Global Load Balancing functions
- Make it dead simple to operate
Using the client is safe. The client is currently hardcoded to a 5 second, timeout. I'll make this configurable if people ask for that, please file a request for any features. Please send feedback! It currently does not cache responses, if this is a feature you'd like earlier rather than later, post a request. The validation of DNSSec is complete including NSEC. As of now NSEC3 is broken, and I may never plan to support it. I have some alternative ideas for private data in the zone.
New ClientFuture is a brand new rewrite of the old Client. It has all the same features as the old Client, but is written with the wonderful futures-rs library.
Unique client side implementations
These are not unique to this client, but are high level functions that hide the details in DNS from the caller
- secure_query - DNSSec validation
- create - atomic create of a record, with authenticated request
- append - verify existence of a record and append to it
- compare_and_swap - atomic (depends on server) compare and swap
- delete_by_rdata - delete a specific record
- delete_rrset - delete an entire record set
- delete_all - delete all records sets with a given name
The server code is complete, the daemon supports IPv4 and IPv6, UDP and TCP. There currently is no way to limit TCP and AXFR operations, so it is still not recommended to put into production as TCP can be used to DOS the service. Master file parsing is complete and supported. There is currently no forking option, and the server is not yet threaded. There is still a lot of work to do before a server can be trusted with this externally. Running it behind a firewall on a private network would be safe.
Zone signing support is complete, to insert a key store a pem encoded rsa file
in the same directory as the initial zone file with the
.key suffix. Note:
this must be only readable by the current user. If one is not present one will
be created and written to the correct location. This also acts as the initial
key for dynamic update SIG(0) validation. To get the public key, the
record for the zone can be queried. This is needed to provide to other
upstream servers to create the
DS key. Dynamic DNS is also complete,
if enabled, a journal file will be stored next to the zone file with the
jrnl suffix. Note: if the key is changed or updated, it is currently the
operators responsibility to remove the only public key from the zone, this
allows for the
DNSKEY to exist for some unspecified period of time during
key rotation. Rotating the key currently is not available online and requires
a restart of the server process.
Currently the root key is hardcoded into the system. This gives validation of DNSKEY and DS records back to the root. NSEC is implemented, but not NSEC3. Because caching is not yet enabled, it has been noticed that some DNS servers appear to rate limit the connections, validating RRSIG records back to the root can require a significant number of additional queries for those records.
Zones will be automatically resigned on any record updates via dynamic DNS.
- RFC 1035: Base DNS spec (partial, caching not yet supported)
- RFC 3596: IPv6
- RFC 2782: Service location
- RFC 6891: Extension Mechanisms for DNS
- RFC 2136: Dynamic Update
Secure DNS operations
- RFC 3007: Secure Dynamic Update
- RFC 4034: DNSSEC Resource Records
- RFC 4035: Protocol Modifications for DNSSEC
- RFC 4509: SHA-256 in DNSSEC Delegation Signer
- RFC 5702: SHA-2 Algorithms with RSA in DNSKEY and RRSIG for DNSSEC
- RFC 6840: Clarifications and Implementation Notes for DNSSEC
- RFC 6944: DNSKEY Algorithm Implementation Status
RFC's in progress or not yet implemented
- RFC 1995: Incremental Zone Transfer
- RFC 1996: Notify slaves of update
- Update Leases: Dynamic DNS Update Leases
- Long-Lived Queries: Notify with bells
Secure DNS operations
- RFC 5155: DNSSEC Hashed Authenticated Denial of Existence
- RFC 6975: Signaling Cryptographic Algorithm Understanding
- DNSCrypt: Trusted DNS queries
- S/MIME: Domain Names For S/MIME
This assumes that you have Rust stable installed. These presume that the trust-dns repos have already been synced to the local system:
$ git clone https://github.com/bluejekyll/trust-dns.git $ cd trust-dns
- openssl development libraries
- sqlite3 development libraries
Mac OS X: using homebrew
$ brew install openssl $ brew install sqlite $ export OPENSSL_INCLUDE_DIR=`brew --prefix openssl`/include $ export OPENSSL_LIB_DIR=`brew --prefix openssl`/lib
Debian-based (includes Ubuntu & Raspbian): using apt-get
$ apt-get install openssl $ apt-get install libssl-dev $ apt-get install libsqlite3-dev
These are good for running on local systems. They will create sockets for local tests, but will not attempt to access remote systems.
$ cargo test
These will try to use some local system tools for compatibility testing, and also make some remote requests to verify compatibility with other DNS systems. These can not currently be run on Travis for example.
$ cargo test -- --ignored
Waiting on benchmarks to stabilize in mainline Rust.
- Production build
$ cargo build --release
Warning: Trust-DNS is still under development, running in production is not recommended. The server is currently only single-threaded, it is non-blocking so this should allow it to work with most internal loads.
- Verify the version
$ target/release/named --version
- Get help
$ target/release/named --help
Why are you building another DNS server?
Because of all the security advisories out there for BIND. Using Rust semantics it should be possible to develop a high performance and safe DNS Server that is more resilient to attacks.
Licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.