[GH-ISSUE #5328] Feature Request: New Lets Encrypt dns-persist-01 Challange #3170

Open
opened 2026-02-26 07:38:01 +03:00 by kerem · 0 comments
Owner

Originally created by @Radiotic on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5328

Is your feature request related to a problem? Please describe.

I deployed NPM on a VPS and It would be really nice to use DNS Validation without the need of configuring DNS API Keys for that. My API provider doesn't let me break down permissions for a key so its basically full access.

Describe the solution you'd like

As far as I understand this is solved by this new LetsEncrypt Validation Method:
https://letsencrypt.org/2026/02/18/dns-persist-01

So it would be really nice if this could be implemented in future releases

Additional context

The Method is not rolled out yet but will come in the next months

Support for the draft specification is available now in Pebble, a miniature version of Boulder, our production CA software. Work is also in progress on a lego-cli client implementation to make it easier for subscribers to experiment with and adopt. Staging rollout is planned for late Q1 2026, with a production rollout targeted for some time in Q2 2026.

Originally created by @Radiotic on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5328 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Is your feature request related to a problem? Please describe.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> I deployed NPM on a VPS and It would be really nice to use DNS Validation without the need of configuring DNS API Keys for that. My API provider doesn't let me break down permissions for a key so its basically full access. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> As far as I understand this is solved by this new LetsEncrypt Validation Method: https://letsencrypt.org/2026/02/18/dns-persist-01 So it would be really nice if this could be implemented in future releases **Additional context** <!-- Add any other context or screenshots about the feature request here. --> The Method is not rolled out yet but will come in the next months >Support for the draft specification is available now in [Pebble](https://github.com/letsencrypt/pebble), a miniature version of [Boulder](https://github.com/letsencrypt/boulder), our production CA software. Work is also in progress on a [lego-cli](https://go-acme.github.io/lego/usage/cli/) client implementation to make it easier for subscribers to experiment with and adopt. Staging rollout is planned for late Q1 2026, with a production rollout targeted for some time in Q2 2026.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#3170
No description provided.