Lego (v4.31-0) has now support for DNS Provider for ISPConfig (DDNS Module) and DNS provider for ISPConfig (without DDNS module?): (Link to Github was not allowed for me , so use Google to find it)
Your point? Ispconfig uses acme.sh preferably or otherwise certbot. Both have been supporting ISPC DNS for a long long time. Though DNS is not used by ispconfig at all by default.
Sorry, my mistake. Shouldnt' have made my first post here, using ISPconfig over 10 years and beiing registered here since 2014. Won't happened again for another 10 years
It's nice to see that the Lego acme client supports ISPConfig DNS API too now. Thank you for bringing this to my attention. Here is the link, which you could not add in your first post. https://github.com/go-acme/lego
Nice, but ISPConfig does not support dns challenge out of box yet, though it can be achieved manually. It however may be added as supported LE client in ISPConfig provided some good volunteers write and propose its plugin, which may be easy, since current supported LE clients, acme.sh and certbot already matured. The only thing which should be considered, if this LE client is later planned to be added, it is best if dns challenge support is included together.
ISPConfig does not need Lego support to make it useful that Lego supports the ISPConfig remote API. Think of non-ISPConfig servers requiring LE certs, Docker containers, etc. where the domain name is managed by an ISPConfig system.
You posted it in the ispconfig forum so I responded from a ispconfig standpoint Ofcourse it's nice that ispconfig gets recognized in Lego too. There are countless of these kind of apps in all kinds of languages. Of which many support ispconfig dns already. And now Lego can be added to the list. On Linux I just stick with acme.sh and on Windows I use Posh-Acme (powershell/dotnet) a lot.
great finding, happy that ispconfig is regonized as proper dns provider as you tend to see only the big providers.
