version bump

CHANGELOG.md

@@ -2,7 +2,7 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 
-## unreleased
+## 0.6.0 2016-06-01
 ### Added
 - Documentation on all modules, and many standard RFC types
 - Authority zone signing now complete, still need to load/save private keys

Cargo.lock

@@ -1,6 +1,6 @@
 [root]
 name = "trust-dns"
-version = "0.5.3"
+version = "0.6.0"
 dependencies = [
  "backtrace 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
  "chrono 0.2.21 (registry+https://github.com/rust-lang/crates.io-index)",

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "trust-dns"
-version = "0.5.3"
+version = "0.6.0"
 authors = ["Benjamin Fry <benjaminfry@me.com>"]
 
 # A short blurb about the package. This is not rendered in any format when
@@ -9,8 +9,7 @@ description = """\
 TRust-DNS is a safe and secure DNS server and client with DNSec support.\
  It is working to be a replacement for BIND9. DNSSec on the client side, with\
  NSEC validation for negative records, is complete. The client and server both\
- support dynamic DNS, SIG0 and TSIG validation are currently a WIP. Full DNSSec\
- on the server is a WIP.\
+ support dynamic DNS with authenticated requests.\
 """
 
 # These URLs point to more information about the repository

README.md

@@ -24,12 +24,26 @@ ground up.
 
 ## Client
 
-Using the client should be safe. The client is currently hardcoded to a 5 second,
+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 it's not clear at this point that it will be supported.
+ is broken, and I may never plan to support it. I have some alternative ideas
+ for private data in the zone.
+
+### 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
 
 ## Server
 
@@ -54,6 +68,8 @@ 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's implemented
 
 ### Basic operations