ACME TXT entry and Plesk XML API?
stilez last edited by stilez
I'll be using certificates on Let's Encrypt, and I'm not sure if the current ACME package does what I need. (If not, I'd hope to discuss the work involved in enhancing it). I'd like to handle ACME by directly adding TXT records.
My current host + domain manager uses Plesk. The Plesk XML API is in use, and I've played around enough to be sure I can use their XML protocol to add the necessary TXT records to my domain programmatically.
But I can't figure out whether the nsupdate method shown in the pfSense docs as 'nsupdate validation' is the same as, or can work with, the XML API method shown in the Plesk XML API docs.
As Plesk is very popular, can someone shed light whether the ACME package can work using nsupdate via the Plesk API (if so how), or does it need enhancing to directly change/create TXT entries in DNS?
Alternatively, given that my host uses Plesk, what programmatic method would ACME/nsupdate usually be expecting to use, to add its TXT records?
That would be a matter of configuring plesk to accept updates via the nsupdate method. Using their API is going to be completely different unless it implements that somehow.
nsupdate is an implementation of a specific protocol, RFC2136.
This is a guide on what is required to get a bind server configured to accept updates:
An alternate strategy might be to set up a bind server like in that link that serves as the master of a dynamic zone with the plesk as the slave but that would preclude managing the zone in plesk which is likely undesirable.
The heavy lifting for this probably needs to be done on the plesk. Instead of accepting updates via their proprietary API they should have a standard method such as RFC2136.