Recently I encountered an issue with DA's LetsEncrypt module.
Turns out when a domain has multiple CAA records, DA's check only checks the first one and then bails if that isn't correct.
See the following situation:
And when I check the DNS:
Sadly, I cannot get rid of those other CAA records, as my DNS provider is CloudFlare for this domain and they enforce them being there.
This seems like a bug in DirectAdmin, as per specification, multiple CAA records are a valid configuration.
Turns out when a domain has multiple CAA records, DA's check only checks the first one and then bails if that isn't correct.
See the following situation:
Code:
root@directadmin:~# /usr/local/directadmin/scripts/letsencrypt.sh request DOMAIN.com
CAA record prevents issuing the certificate: "comodoca.com"
And when I check the DNS:
Code:
$ dig IN CAA DOMAIN.com @8.8.8.8
; <<>> DiG 9.16.1-Ubuntu <<>> IN CAA DOMAIN.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15567
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;DOMAIN.com. IN CAA
;; ANSWER SECTION:
DOMAIN.com. 3189 IN CAA 0 issue "comodoca.com"
DOMAIN.com. 3189 IN CAA 0 issue "digicert.com"
DOMAIN.com. 3189 IN CAA 0 issue "letsencrypt.org"
DOMAIN.com. 3189 IN CAA 0 issuewild "comodoca.com"
DOMAIN.com. 3189 IN CAA 0 issuewild "digicert.com"
DOMAIN.com. 3189 IN CAA 0 issuewild "letsencrypt.org"
Sadly, I cannot get rid of those other CAA records, as my DNS provider is CloudFlare for this domain and they enforce them being there.
This seems like a bug in DirectAdmin, as per specification, multiple CAA records are a valid configuration.