community
/
dns
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update the readme

This commit is contained in:
Miek Gieben 2012-05-03 08:59:02 +02:00
parent 7562c68094
commit 901be67f92
2 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.markdown
View File

@ -2,10 +2,11 @@
> Less is more.
Complete and usable DNS library. Most widely used Resource Records are
Complete and usable DNS library. All widely used Resource Records are
supported, including the DNSSEC types. It follows a lean and mean philosophy.
If there is stuff you should know as a DNS programmer there isn't a convenience
function for it.
function for it. Server side and client side programming is supported, i.e. you
can build servers and resolvers with it.
## Goals:
@ -18,12 +19,12 @@ function for it.
* UDP/TCP queries, IPv4 and IPv6;
* RFC 1035 zone file parsing;
* Fast:
* reply speed around 35/40K qps (Faster hardware -> more qps);
* Reply speed around 35/40K qps (faster hardware results in more qps);
* Parsing RRs (zone files) with 95/100K RR/s, that's 5M records in about 50 seconds;
* This is expected to be optimized further.
* Client and server side programming (mimicking the net/http package);
* Asynchronous queries/replies for client and server;
* DNSSEC;
* DNSSEC: signing, validating and key generation for DSA, RSA and ECDSA;
* EDNS0, NSID;
* AXFR/IXFR;
* TSIG;
@ -100,7 +101,7 @@ to the table in how to layout the directory structure.
## Supported RFCs
All of them:
*all of them*
* 103{4,5} - DNS standard
* 1982 - Serial Arithmetic
@ -132,10 +133,9 @@ All of them:
* 5155 - NSEC3 record
* 5205 - HIP record
* 5702 - SHA2 in the DNS
* 5933 - GOST
* 5936 - AXFR
* xxxx - ECDSA
* xxxx - URI record
* 6605 - ECDSA
* xxxx - URI record (draft)
## Loosely based upon:

5
TODO.markdown
View File

@ -5,13 +5,12 @@ need to be fixed.
* Speed, we can always go faster. A simple reflect server now hits 35/45K qps
* go test; only works correct on my machine
* Add handy zone data structure (r/b tree)? Or not...
* privatekey.Precompute() when signing?
* Add source/dest and RTT timing in dns.Msg structure???
## Examples to add
* Nameserver, with a small zone, 1 KSK and online signing;
* Recursor - ala FunkenSturm?