- Joined
- Feb 27, 2003
- Messages
- 8,525
Hi guys,
If you wish to test out the 70+ "dns providers", just update Let's Encrypt to 2.0 using CustomBuild script.
This is currently only at the User Level, where, when creating the cert, once "wildcard"option, a new field (below) will appear, defauting to "Dns Provider = Local".
This requires the latest pre-release binaries plus letsencrypt.sh 2.0, and we'll be added fixes/improvements as we go.
You can then pick a new dns provider, say "CloudFlare" and enter your user/key + extra bits, as needed, specified by that provider.
Once used, and you trigger the request.. the envs are added and the new letsencrypt.sh should pick that up and use it instead of the local dns box.
Feature is listed here, so look for any changes, which can happen if we need to alter the design:
It can also inherit reseller-defined DNS provider or a global one for all the domains.
Thanks and happy testing!
John
If you wish to test out the 70+ "dns providers", just update Let's Encrypt to 2.0 using CustomBuild script.
This is currently only at the User Level, where, when creating the cert, once "wildcard"option, a new field (below) will appear, defauting to "Dns Provider = Local".
This requires the latest pre-release binaries plus letsencrypt.sh 2.0, and we'll be added fixes/improvements as we go.
You can then pick a new dns provider, say "CloudFlare" and enter your user/key + extra bits, as needed, specified by that provider.
Once used, and you trigger the request.. the envs are added and the new letsencrypt.sh should pick that up and use it instead of the local dns box.
Feature is listed here, so look for any changes, which can happen if we need to alter the design:
It can also inherit reseller-defined DNS provider or a global one for all the domains.
Thanks and happy testing!
John