SSL constant failure emails for one domain

jigster

Verified User
Joined
Jul 23, 2021
Messages
127
I have a few domains using external nameservers who's DNS resolves to my server for just mail. and webmail. hostnames. All other records (www etc) point elsewhere. This works correctly with the new acme ssl system: the hostnames not resolving to my server fail the ssl http check, and a cert is issued for just mail. and webmail. All good.

Except for one domain, which is constantly sending failure notifications. This domain is set up exactly the same as the others, with mail. and webmail. pointing to my server, and all other records pointing elsewhere. But for this domain, it is constantly trying to provision a cert for ftp., even though this does NOT point to my server. The only difference I can see with this domain is that there is actually no DNS record set up at all for 'ftp' (whereas the other domains have it set up but pointing elsewhere).

If I remove ftp from the DirectAdmin setting letsencrypt_list, everything works correctly for this domain, but I can't do this because that setting is global and i need it in there for other domains.

Why would the automatic certificate provisioning keep trying for a hostname that doesn't even have a DNS record set up? How can I fix this? Thanks for any advice!
 
letsencrypt_list is only the global candidate list; it does not prove every name has an explicit DNS record. I would first query from the DA host, including IPv6 and wildcard DNS:
dig +short ftp.example.tld A
dig +short ftp.example.tld AAAA
dig +short random-test.example.tld A
dig +short random-test.example.tld AAAA
A wildcard A/AAAA record (or stale resolver cache) can make ftp appear resolvable even when there is no explicit ftp record.
On DA 1.710+ also check Account Manager -> SSL/TLS Certificates -> Provisioning history. Open the failed job and confirm the exact SAN list and validation error. That page was added specifically for automatic ACME attempts: DirectAdmin 1.710 changelog.
If ftp is queued while the authoritative result is genuinely NXDOMAIN for both A and AAAA, this looks like a selector bug in the new automatic certificate flow, not something you should solve by removing ftp globally. I would report it with the DA version and provisioning-history details.
 
Back
Top