DNS-PERSIST-01 Explained: Record and Status
Short answer: DNS-PERSIST-01 is a new ACME challenge type. Instead of creating a fresh _acme-challenge TXT record for every certificate, you publish one TXT record at _validation-persist.example.com that names the certificate authority and your ACME account. As long as the record stays, that account can get certificates for the domain without touching DNS again. The CA/Browser Forum allowed the method in October 2025 (ballot SC-088v3), and Let's Encrypt announced support in February 2026. As of November 2026 the specification is still an IETF draft (version -02), and Let's Encrypt's documentation does not list it among its live challenge types yet. Until it is, the way to automate DNS validation is DNS-01 with a DNS API.
How DNS-PERSIST-01 works
With today's DNS-01 challenge, the CA gives your ACME client a new token for every order. The client puts a value derived from it into a TXT record at _acme-challenge.<domain>, the CA checks it, and the record is removed. Every issuance and every renewal needs write access to your DNS.
DNS-PERSIST-01 turns this into a one-time setup. You publish a TXT record once:
_validation-persist.example.com. IN TXT ("authority.example;"
" accounturi=https://ca.example/account-hash/sha-256/5SQm7n6tPh2-PlLbCKGnViTXX5z19SCN4cPGQHSk-kw")
This is the example from the current draft. The record says two things:
- Which CA may use it: the issuer domain name at the start, the same syntax as a CAA record.
- Which ACME account it authorizes:
accounturi. In the current draft this is a hash computed from your domain, your account URL and your account key, so the record does not publish the account URL itself. Let's Encrypt's February 2026 announcement showed the plain account URL from an earlier draft, so expect the exact value to come from your ACME client rather than typing it by hand.
When that account orders a certificate, the CA looks up the record, sees its own name and the matching account, and the domain is validated. Your ACME client needs no DNS credentials at all.
Wildcards and subdomains
Without extra options, the record validates only the exact name it is published for. Add policy=wildcard to also cover *.example.com and subdomains such as www.example.com or server.dept.example.com:
_validation-persist.example.com. IN TXT ("authority.example;"
" accounturi=…" " policy=wildcard")
Expiry
An optional persistUntil=<unix time> tells the CA to stop relying on the record after that moment. It limits the damage of a forgotten record, but if you set it, put a reminder in place: once it passes, renewals stop until you update the record.
Got an idea? Find the perfect domain for it
Our AI domain name generator suggests available names across hundreds of extensions. Free SSL, DNS and Whois privacy included.
DNS-01 and DNS-PERSIST-01 compared
| DNS-01 | DNS-PERSIST-01 | |
|---|---|---|
| Record | TXT at _acme-challenge.<domain> | TXT at _validation-persist.<domain> |
| Changes per certificate | A new value for every order | None after the first setup |
| DNS credentials on the server | Needed for every renewal | Not needed |
| Wildcards | Yes | Yes, with policy=wildcard |
| What an attacker needs | Write access to your DNS | Your ACME account key |
| Status (Nov 2026) | Supported by every major CA and client | IETF draft; Let's Encrypt support announced |
Security trade-offs
- The account key becomes the key to your domain. Anyone holding it can get certificates for every domain whose record names that account, immediately and without touching DNS. Keep it off shared machines and back it up like a private key.
- Revoking access: deleting the record works once resolver caches expire; deactivating the ACME account works at once.
- Subdomains:
policy=wildcardcovers every name under the domain, including subdomains you hand to other people or services. Leave it off if that matters. - DNS security: the draft asks CAs to use DNSSEC-validating resolvers, and a DNSSEC failure fails the challenge.
When can you use it?
- October 2025: CA/Browser Forum ballot SC-088v3, "DNS TXT Record with Persistent Value", passed; the IETF ACME working group adopted the draft the same month.
- February 18, 2026: Let's Encrypt announced it is implementing the method, with staging planned for late Q1 2026 and production for Q2 2026. Its test CA, Pebble, already supported it, and a lego client implementation was in progress.
- September 20, 2026: draft-ietf-acme-dns-persist-02 published. It is still a draft, not an RFC.
- November 2026: Let's Encrypt's challenge types page and its upcoming features page do not mention DNS-PERSIST-01. Check them before you plan around it.
Client support follows the CA: once Let's Encrypt enables it, expect lego first. Certbot, acme.sh, cert-manager and Caddy had not announced support when we wrote this.
What to do until then
Use DNS-01 with a DNS provider that has an API, and give the ACME client a key that can only change DNS records. Our guide Let's Encrypt DNS-01 challenge with certbot and lego has a ready hook script for the NameOcean API. If your domain uses NameOcean DNS, you can also skip the client entirely: we issue and renew a free wildcard Let's Encrypt certificate for it, from the dashboard or with one API call.
FAQ
What is the DNS-PERSIST-01 release date?
Let's Encrypt targeted Q2 2026 for production. As of November 2026 its documentation does not list the challenge as available, so there is no confirmed date. Watch the Let's Encrypt blog and its challenge types page.
Do I still need DNS API credentials with DNS-PERSIST-01?
Only to publish the record once, and you can do that by hand. Renewals need no DNS access.
Can several CAs use the same domain?
Yes. Each CA gets its own TXT record at the same name, each with its issuer name and account.
Is DNS-PERSIST-01 less secure than DNS-01?
It moves the risk. DNS-01 puts DNS credentials on every server that renews certificates; DNS-PERSIST-01 removes them but makes the ACME account key enough on its own. Which is safer depends on which secret you protect better.
Sources
- draft-ietf-acme-dns-persist (IETF)
- Let's Encrypt: DNS-PERSIST-01 announcement (February 18, 2026)
- Let's Encrypt: challenge types
Need certificates now? Find a domain below and get a free wildcard certificate with it.
Got an idea? Find the perfect domain for it
Our AI domain name generator suggests available names across hundreds of extensions. Free SSL, DNS and Whois privacy included.