New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Create DNS record automatically #1228
Comments
I can see this being way more complex than at first sight. What if there is a different A-record? Update or not?, what if there is a c-name already, update or not? Removing can be tricky, if its been manually changed do we leave or remove? If you are looking for an easy solution to the home server problem, do what many do for home use, make a wildcard DNS entry pointing to home, then you only need specific DNS to override that wildcard IP for things not on your home IP. Leaving you the ability to make up hostnames in your home NPM on the fly that will work immediately for SSL creation and in your web browser. |
Thanks! |
The DNS challenge is performed by certbot, a library by the organization behind LetsEncrypt. So re-implementing all the logic for DNS record creation would be a huge untertaking and would lead once again to lots of requests to add support for a very specific provider. So unless someone from the community would want to spend his time implementing this, I don't think it is likely to be added. |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
It will be great to have this feature to automatically create a DNS record to the domain provider when adding a proxy host.
The Certificates DNS Challenger already supports a vast range of DNS providers. Having the above feature won't be a big issue... i suppose. :)
The text was updated successfully, but these errors were encountered: