This is great news for those of us who want to see DNSSEC more widely deployed for three reasons:<p>1. CloudFlare already hosts the DNS for millions of domains.  This is now making it VERY easy for those who use CloudFlare to sign their domains with DNSSEC.<p>2. Because of the competition within the DNS hosting &#x2F; operator space, this move by CloudFlare will hopefully motivate the other large DNS operators to simplify their own user experience for DNSSEC.<p>3. For those of us who want to see stronger crypto within DNSSEC, this move by CloudFlare advances the use of an elliptic curve algorithm.  Yes, ECDSA has its issues, but by getting it out there: a) it gets people looking at EC algorithms; and b) it gets software providers realizing they need to have their user interfaces adaptable to incorporate more DNSSEC algorithms. (I.e. to realize the list is NOT fixed and will grow over time.)<p>As I said in another comment ( <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10553383" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10553383</a> ) there <i>is</i> a draft out there to add Ed25519 as a DNSSEC algorithm:<p><a href="https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;draft-sury-dnskey-ed25519-01" rel="nofollow">https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;draft-sury-dnskey-ed25519-01</a><p>This draft needs to be approved through the IETF working groups - and then deployed on both the <i>signing</i> and <i>validation</i> sides of DNSSEC.  This will take quite some time and so we need to start as soon as we can.