Obligatory responses to tptacek&#x27;s article:<p>- <a href="http:&#x2F;&#x2F;blog.easydns.org&#x2F;2015&#x2F;08&#x2F;06&#x2F;for-dnssec&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.easydns.org&#x2F;2015&#x2F;08&#x2F;06&#x2F;for-dnssec&#x2F;</a><p>- <a href="http:&#x2F;&#x2F;www.circleid.com&#x2F;posts&#x2F;20150318_is_dnssec_worth_the_effort&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.circleid.com&#x2F;posts&#x2F;20150318_is_dnssec_worth_the_e...</a><p>Collectively <i>thousands</i> of words have been written on this topic within HN - and there are stark divisions between those who oppose DNSSEC and those who believe DNSSEC is a helpful and useful method of adding a layer of security to the Internet.<p>We don&#x27;t agree.  We won&#x27;t agree.<p>Meanwhile, those of us who want to see DNSSEC more widely deployed applaud this move by CloudFlare because it both makes deployment simpler for many people and also advances the usage of stronger crypto (ECDSA) within DNSSEC.<p>This is great news!