Hacker News
points by alwillis 2 days ago | 0 comments
Automatic Certificate Management Environment (ACME), RFC 8555, recommends certificate issuers use DNSSEC when using DNS to validate control of the DNS zone:

  As noted above, DNS forgery attacks against the ACME server can
  result in the server making incorrect decisions about domain control
  and thus mis-issuing certificates.  Servers SHOULD perform DNS
  queries over TCP, which provides better resistance to some forgery
  attacks than DNS over UDP.
    
    An ACME-based CA will often need to make DNS queries, e.g., to [1]
  validate control of DNS names.  Because the security of such
  validations ultimately depends on the authenticity of DNS data, every
  possible precaution should be taken to secure DNS queries done by the
  CA. Therefore, it is RECOMMENDED that ACME-based CAs make all DNS
  queries via DNSSEC-validating stub or recursive resolvers.  This
  provides additional protection to domains that choose to make use of
  DNSSEC.
  
  An ACME-based CA must only use a resolver if it trusts the resolver
  and every component of the network route by which it is accessed.
  Therefore, it is RECOMMENDED that ACME-based CAs operate their own
  DNSSEC-validating resolvers within their trusted network and use
  these resolvers both for CAA record lookups and all record lookups in
  furtherance of a challenge scheme (A, AAAA, TXT, etc.).
  
  
[1]: https://www.rfc-editor.org/info/rfc8555/#section-11.2
[–] tptacek 1 day ago
That's saying less than it appears to. What the RFC is saying is that CAs should be validating DNSSEC where it exists. It was written at a time when CAs didn't uniformly validate DNSSEC at all (because DNSSEC causes outages and pisses off customers). Even I think CAs should validate DNSSEC where it exists! It is not a general recommendation that everyone sign their zones, though.
Hacker News