IT Security

NOVEMBER 2026

Persistent DNS: Actalis simplifies domain validation with dns-persist-01

A stable DNS record to reduce repeated validation steps and support SSL/TLS certificate automation.

Actalis is expanding its domain validation methods with dns-persist-01, a new option for organizations looking to simplify and streamline SSL/TLS certificate management. The benefit is clear: a persistent DNS record can be configured once and reused for subsequent validations, without having to replace it for every new challenge.

Shorter certificate lifetimes call for automated processes

The maximum validity period of publicly trusted SSL/TLS certificates is being progressively reduced: from March 15, 2026, it is 200 days; it will decrease to 100 days on March 15, 2027, and to 47 days on March 15, 2029. More frequent renewals require reliable processes that minimize repetitive tasks and reduce the risk of service interruptions.

Automating certificate requests is an important step. However, an effective process must also cover domain validation, certificate installation and expiration monitoring. dns-persist-01 addresses the validation stage, simplifying one of the steps that may require coordination across multiple teams.

What is dns-persist-01 and how does it work?

Before issuing a certificate, a Certification Authority (CA) must verify that the applicant controls the domains to be included. This process is known as Domain Control Validation (DCV).

dns-persist-01 is an ACME domain validation method based on a persistent DNS TXT record. The record is published under the _validation-persist name of the relevant domain and associates the authorization with a specific Certification Authority and ACME account.

The CA can check the same record during subsequent validations without requiring a new DNS value for each challenge. The record must remain present and valid: persistent does not mean unlimited validation, nor does it eliminate other checks required for certificate issuance.

The method is described in an IETF specification currently published as an Internet-Draft and still under development.

How does it differ from http-01 and dns-01?

Within the ACME protocol, validation methods differ in where proof of domain control is published and in the operational steps required to automate the process.

Domain validation: ACME methods compared
ACME method How validation works Operational impact
http-01 The client makes a validation response available on a web server accessible via HTTP. Requires the HTTP service to be reachable. Does not support wildcard domain validation.
dns-01 The client publishes a TXT record under _acme-challenge containing the challenge value. Supports wildcard certificates. Each new challenge requires a dedicated DNS value; automation can use DNS APIs or delegation.
dns-persist-01 The CA checks a persistent TXT record associated with the CA and ACME account. Reduces recurring DNS changes. Wildcard coverage depends on the configured authorization scope.

A new challenge is not necessarily required for every certificate issuance: an existing valid authorization may be reused within the applicable limits. The benefit of dns-persist-01 becomes particularly relevant when a new validation is required, as the DNS record can remain unchanged.

Other Actalis domain validation methods

In addition to ACME challenges, Actalis procedures support publishing a file on an HTTP server, creating a TXT record and, for domains registered and managed by Aruba, checking the relevant database.

Email-based validation, on the other hand, is being phased out. From March 15, 2026, the CA/Browser Forum Baseline Requirements discourage the use of standard domain email addresses and email contacts published in DNS CAA or TXT records. From March 15, 2028, these methods will no longer be permitted, nor will previously obtained validations using these methods be reusable for new certificate issuance. This is another reason to move towards automation-friendly methods, such as DNS-based validation.

The most suitable method depends on how domains, DNS and web servers are managed. To automate operations effectively, it is important to choose an approach compatible with the tools in use and the available permissions. The Actalis domain validation guide describes the procedures available for different services.

Fewer DNS changes, greater operational continuity

Persistent DNS is particularly useful when domain management and certificate management are handled by different teams or service providers. Reducing recurring changes can mean fewer operational requests, less coordination and a renewal process that is easier to automate.

Protecting the ACME account key and keeping authorizations up to date remain essential. The record is linked to a specific account, so creating a new account may require updating the DNS configuration. Removing the record also does not revoke certificates that have already been issued.

From domain validation to certificate lifecycle management

The introduction of dns-persist-01 is part of Actalis' ongoing efforts to make certificate management increasingly automated. The ACME protocol enables automated certificate issuance and renewal requests, while centralized management with Actalis CertiManager helps organizations manage certificates and expiration dates.

Validation, issuance and deployment across systems should be designed as parts of a single process. Choosing the right validation method is a practical step towards preparing for shorter certificate lifecycles.

Interested in using dns-persist-01 within your organization? Contact Actalis to learn more about how it works and identify the most suitable approach for managing your certificates.

Product added to compare.