mod_md v2.4.21

• MDChallengeDns01 can now be configured for individual domains.
  Using PR from Jérôme Billiras (@bilhackmac) and adding test case and fixing proper working
• Fixed a bug found by Jérôme Billiras (@bilhackmac) that caused the challenge
  teardown not being invoked as it should.

mod_md v2.4.20

• Enabling ED25519 support and certificate transparency information when
  building with libressl v3.5.0 and newer. Thanks to Giovanni Bechis.

mod_md v2.4.19

• restored curl_easy cleanup behaviour from v2.4.14 and refactored
  the use of curl_multi for OCSP requests to work with that. Fixes #293.

mod_md v2.4.18

• New directive MDStoreLocks that can be used on cluster setups with
  a shared file system for MDStoreDir to order activation of renewed
  certificates when several cluster nodes are restarted at the same time.
  Store locks are not enabled by default.

mod_md v2.4.17

• A bug was fixed that caused very large MDomains with the combined DNS
  names exceeding ~7k to fail, as request bodies would contain partially
  wrong data from uninitialized memory. This would have appeared as
  failure in signing-up/renewing such configurations.
  This was reported by Ronald Crane (Zippenhop LLC).

mod_md v2.4.16

• The MDCertificateAuthority directive can take more than one URL/name of
  an ACME CA. This gives a failover for renewals when several consecutive attempts
  to get a certificate failed. See REAME for details.
• New directive MDRetryDelay to set the delay of retries. See README
  for details.
• New directive MDRetryFailover to set the number of errored attempts
  before an alternate CA is selected for certificate renewals. See README
  for details.

mod_md v2.4.15

• Fixed a bug leading to failed transfers for OCSP stapling information
  when more than 6 certificates needed updates in the same run.

mod_md v2.4.14

• Added support for tailscale (https://tailscale.com) certificates to have
  trusted access to your internal domain names. See README.md for more
  information on how to set this up.
• Fix for a memory leak in handling of JSON arrays. This leak was mainly
  triggered by the additions to the server-status handler and lead to
  increased process sizes with each request of a status page.

mod_md v2.4.13

• A possible NULL pointer deref was fixed in the JSON code for
  persisting time periods (start+end). Fixes #282.
  Thanks to @marcstern for finding this.

mod_md v2.4.12

• Implement full auto status ("key: value" type status output).
  Especially not only status summary counts for certificates and
  OCSP stapling but also lists. Auto status format is similar to
  what was used for mod_proxy_balancer.
  [Rainer Jung]