Search K
Appearance
Appearance
Released: 2026-08-18
acme_dns_names_per_cert configuration option in directadmin.conf new Controls the maximum number of DNS names that the ACME system can combine into a single TLS certificate.
The pages for showing and updating TLS certificates show decoded certificate information side-by-side with the PEM blocks.

The page for creating a certificate signing request (CSR) now shows the private key that should be used with the acquired certificate.

The new ACME system logic for splitting out DNS names into different certificate files is slightly updated.
Domains that use HTTP ACME challenge will attempt to cover all DNS names in a single certificate file if possible. It is limited by the new acme_dns_names_per_cert configuration option (the default is 25). If there are more DNS names that should be covered, then each subdomain will start using a separate certificate file.
Wildcard certificates will cover the main domain and first-level subdomains in a single certificate. Deeper subdomains will use a separate certificate file.
The check to detect if the server will be able to use the ACME DNS challenge (and wildcard certificates) is extended to detect situations when the DNS challenge is blocked by the _acme-challenge CNAME record.
The page for creating a self-signed certificate allows selecting a key type.
Creating a self-signed certificate is a first step before a certificate signing request (CSR) can be generated. Selecting a custom key type for the self-signed certificate allows creating CSRs for different key types.

A new maintenance task is added to list all users who are still using the old TLS system. The fix action reconfigures all user domains to start using the new TLS system.

Maintenance tasks can be found at the Administrator level -> Admin tools -> Maintenance.
6.3.6-6 to 6.3.6-810.6.27 to 10.6.284.28.0 to 4.29.01.9.1 to 1.9.21.6.3 to 1.6.515.09 to 15.111.3.9c to 1.3.9d8.10.0 to 8.10.11.7.2 to 1.7.32.0.0 to 2.1.00.17.0 to 0.18.0