Hold on. This is actively conflating DNSSEC and DANE.
I know your point that the "main feature" of DNSSEC is enabling DANE, and I respect that. But the two domains are still distinct: DNS security and the PKI built on top of that.
DNSCrypt only addresses DNS security, so it should be compared to pure DNSSEC, which obviously does not "cede to the US Government control over TLS keys".
Bad reasoning. You think we'll not deploy HTTP/2 because the head of the committee works for Akamai? Cmon.
DNSCrypt needs a secure resolver and client software. CloudFlare doesn't have either of those things which rather hampers us deploying DNSCrypt.
Behold:
* https://github.com/bitbeans/SimpleDnsCrypt
I'm sure with Filo on your team you could make that happen.
What does CloudFlare have to distribute?
They also open sourced client implementations for end boxes to talk to them or any other recursive securely.
jedisct1 is also looking for work right now, he'd happily implement it all for you I'm sure.
How do both compare ("far better")?
DNSSEC is for server-server, to propagate existing addressbook.
Only DNSCrypt protects your privacy!You don't use Cloudflare as a DNS provider. Their value proposition [imho] is as a CDN/WAF.
I was genuinely hoping someone like Sucuri or Incapsula had picked it up.
We are among the fastest if not the fastest authoritative DNS provider in the world.
We don't provide split horizon DNS, that's correct. That is easily resolved for more orgs by running our own internal DNS if you need that.
http://www.datanyze.com/market-share/DNS/ claims we have 42% of the top 1M domains using our DNS. I'm not sure I actually believe that number, but a lot of people use us for their DNS.