About Daplie: We're taking back the Internet! -------------- Down with Google, Apple, and Facebook! We're re-decentralizing the web and making it read-write again - one home cloud system at a time. Tired of serving the Empire? Come join the Rebel Alliance: jobs@daplie.com | [Invest in Daplie on Wefunder](https://daplie.com/invest/) | [Pre-order Cloud](https://daplie.com/preorder/), The World's First Home Server for Everyone le-challenge-dns ================ [](https://gitter.im/Daplie/letsencrypt-express?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) | [letsencrypt](https://github.com/Daplie/node-letsencrypt) (library) | [letsencrypt-cli](https://github.com/Daplie/letsencrypt-cli) | [letsencrypt-express](https://github.com/Daplie/letsencrypt-express) | [letsencrypt-koa](https://github.com/Daplie/letsencrypt-koa) | [letsencrypt-hapi](https://github.com/Daplie/letsencrypt-hapi) | **For production** use [`le-challenge-ddns`](https://github.com/Daplie/le-challenge-ddns) (or a similar ddns tool) A manual (interactive CLI) dns-based strategy for node-letsencrypt for setting, retrieving, and clearing ACME DNS-01 challenges issued by the ACME server Prints out a subdomain record for `_acme-challenge` with `keyAuthDigest` to be tested by the ACME server. You can then update your DNS manually by whichever method you use and then press [enter] to continue the process. ``` _acme-challenge.example.com TXT xxxxxxxxxxxxxxxx TTL 60 ``` Install ------- ```bash npm install --save le-challenge-dns@2.x ``` Usage ----- ```bash var leChallengeDns = require('le-challenge-dns').create({ debug: false }); var LE = require('letsencrypt'); LE.create({ server: LE.stagingServerUrl // Change to LE.productionServerUrl in production , challengeType: 'dns-01' , challenges: { 'dns-01': leChallengeDns } , approveDomains: [ '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 options * `loopback(defaults, domain, challange, done)` performs a dns lookup of the txt record * `test(opts, domain, challange, keyAuthorization, done)` runs set, loopback, remove, loopback