LetsEncrypt 2.0 with 70+ dnsproviders, ready for testing

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
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
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
9,305
Location
LT, EU
I check via CLI "openssl version"
OpenSSL 1.0.2k-fips 26 Jan 2017
Should i update it manually?
I am using VPS
And now check rpm -q --last openssl to see when it was updated :) I bet it is not 2017.

 

kadek_mentik

Member
Joined
Jun 5, 2020
Messages
52
Location
Bali, Indonesia
@smtalk
i just checked with the command
"openssl-1.0.2k-19.e17.x86_64 sun may 24 13:01:39 2020"
yes,,, 2020 version,,, so my current version is too old, 3 years ago

how to do sir,,,

Regards Sir
 
Top