DNS Challenge vs HTTP

[Nummer378]

@Nummer378

I also looked at the spec right now and I don't see an obvious problem with restricting issuance via CAA in this case. RFC8659 simplified the path traversal algorithm, which previously required checking both the original FQDN tree and all CNAME trees. Checking the CNAMEs is now optional, but you always have to check the FQDN tree of the original, "before CNAME", domain. This is both in RFC6844 and 8659.

As I understand OP, they have to point _acme-challenge.www.example.com to an external hosting provider. They might also have to point www.example.com via CNAME to the hosting provider, @gsloop has not clarified this as I understand this thread. However, even if that is the case it is still possible to put a CAA record on the SLD example.com, which is very likely not CNAME'd.

A CAA issuewild ";" on either www.example.com or example.com prohibits any CA from issuing a wildcard for the corresponding FQDNs and subtrees of it. This applies independently of whether www.example.com (or a subtree of it) is pointed via CNAME to someone else. The CAA climbing algorithm always checks up to the TLD of the FQDN to be validated.

I just realized a possible issue with this:

While the CAA checker algorithm in RFC 8659 does walk up the original FQDN tree, it does stop at the first found CAA record. In addition, it does assume that resolvers follow CNAMEs during existance checking of a CAA record.

This creates a potential problem:

If www.example.com is CNAME'd to evil.com, the operator of evil.com can set a malicious CAA record on evil.com, which will be found before the CAA of example.com is checked. CAA checking stops on the first result. A CAA record on www.example.com is impossible due to the CNAME. Therefore, in this case a restriction via CAA appears to be indeed impossible and @rmbolger is right. (IIRC, this used to be catched by the old RFC 6844 algorithm, but the newer one doesn't seem to support this use case anymore)

(If there is no CNAME on www.example.com all of this does not apply)

---

@gsloop

I don't have a need right now, but it's possible I'd want to issue a wildcard certificate myself for the root (*.example.com). If I setup a CAA then I can't do that, right?

The specifics really depend on your exact setup, which CAA record is where. A domain can have much more than one CAA record and they allow for various settings.

In particular, there's an extension to the CAA specification (RFC 8657), which allows for restrictions by ACME accounts. Let's Encrypt does not currently support this, but has plans to do so. With this feature, you can forbid anyone but yourself from issuing wildcards.

Without the extension, you can still play around with various combinations of CAA records, which might allow what you are looking for. In particular with a CAA record set only on www.example.com it does not apply to example.com.