Centralized DNS Provider / ACME Configuration Profiles

The problem

Currently, when requesting Let's Encrypt certificates via DNS-01 challenge, users have to manually enter the provider-specific configuration (such as API keys, tokens, custom DNS servers, and propagation delays) every single time for each new certificate.
​For environments with multiple domains or frequent certificate additions, this approach is repetitive, error-prone, and makes updating rotated API keys tedious, as they have to be changed individually per certificate.

​Proposed Solution

​Introduce a centralized "DNS Profiles" or "ACME Configurations" management tab within the Nginx Proxy Manager UI (similar to how Access Lists or SSL Certificates are managed).

1. Centralized Storage: Define and save a DNS provider configuration once (e.g., Cloudflare API Token, Hetzner API Key, local RFC 2136 TSIG keys, custom DNS servers).
2. Define and save a DNS provider configuration once (e.g., Cloudflare API Token, Hetzner API Key, local RFC 2136 TSIG keys, custom DNS servers).
3. ​Reusability: When adding or renewing an SSL certificate via DNS-01, instead of filling out the text area manually, the user can simply select a predefined profile from a dropdown menu.
4. ​Global Updates: If an API key or a propagation delay needs to be adjusted, it can be updated in the central profile, instantly applying to all associated certificates.

​Alternative Solutions Considered

​Manually copying and pasting configuration strings from an external password manager or documentation every time a new certificate is created.

​Additional Context

​This feature would massively improve the UX for power users, DevOps setups, and home lab environments that rely heavily on automated wildcard certificates via ACME / RFC 2136 DNS challenges.

No files or tests are named. Start by tracing the existing SSL Certificates and Access Lists management flows, then determine how DNS profiles would be stored and associated with certificates. Done means users can define a provider configuration once, select it for DNS-01 certificates, and update it centrally for associated certificates.