05950414ea | ||
---|---|---|
.gitignore | ||
LICENSE | ||
README.md | ||
index.js | ||
package.json | ||
test.js |
README.md
| letsencrypt (library) | letsencrypt-cli | letsencrypt-express | letsencrypt-koa | letsencrypt-hapi |
le-challenge-ddns
A dns-based strategy for node-letsencrypt for setting, retrieving, and clearing ACME DNS-01 challenges issued by the ACME server
It creates a subdomain record for _acme-challenge
with keyAuthDigest
to be tested by the ACME server.
_acme-challenge.example.com TXT xxxxxxxxxxxxxxxx TTL 60
- Safe to use with node cluster
- Safe to use with ephemeral services (Heroku, Joyent, etc)
Install
npm install --save le-challenge-ddns@2.x
Usage
var leChallengeDdns = require('le-challenge-ddns').create({
email: 'john.doe@example.com'
, refreshToken: '...'
, ttl: 60
, debug: false
});
var LE = require('letsencrypt');
LE.create({
server: LE.stagingServerUrl // Change to LE.productionServerUrl in production
, challengeType: 'dns-01'
, challenges: {
'dns-01': leChallengeDdns
}
, approvedDomains: [ 'example.com' ]
});
NOTE: If you request a certificate with 6 domains listed, it will require 6 individual challenges.
Exposed Methods
For ACME Challenge:
set(opts, domain, challange, keyAuthorization, done)
get(defaults, domain, challenge, done)
remove(defaults, domain, challenge, done)
Note: get()
is a no-op for dns-01
.
For node-letsencrypt internals:
getOptions()
returns the internal defaults merged with the user-supplied optionsloopback(defaults, domain, challange, done)
performs a dns lookup of the txt recordtest(opts, domain, challange, keyAuthorization, done)
runs set, loopback, remove, loopback