CurveDNS is a forwarder nameserver that adds DNSCurve to DNS,
and the first publicly released forwarding implementation
that implements the DNSCurve protocol.

It is a project of Harm van Tilburg (TU Eindhoven).
Jeroen Scheerder and Lieuwe Jan Koning.
=> http://curvedns.on2it.net/about

DNSCurve is a security protocol superior to DNSSEC, but
addressing different and more known vulnerabilities in the DNS.
Besides that it's far more practical to deploy.
It was designed D.J.Bernstein, notable for qmail and tinydns.
=> http://dnscurve.org/

The protocol was described in an RFC-draft by Matthew Dempsky.
=> http://tools.ietf.org/html/draft-dempsky-dnscurve-01

Because the public key part of the FQDN of the authoritive
nameserver, it's pretty much compatible with each tested TLD.
=> http://dns-lab.com/pub/dnscurve/registry-compatibility.lasso

So also mind it can add a considerable portion of security to
internal networks to.


Technically DNSCurve and DNSSEC can co-exist without problem,
in reality it seems to make ego's clash problematicly.


Articles:

DJB exposing DNSSEC is relative:
=> http://cr.yp.to/talks/2009.08.10/slides.pdf

Paul Vixie 'striking' back:
=> http://www.isc.org/community/blog/201002/whither-dnscurve
 
Heated discussion:
=> http://www.cricketondns.com/post.cfm/dnssec-vs-dnscurve

OpenDNS adopts DNSCurve:
=> http://blog.opendns.com/2010/02/23/opendns-dnscurve/

Fix: Please use enclosed .shar file to replicate.

Patch attached with submission follows: