# DNS validation for Let's Encrypt?

**URL:** <https://meta.discourse.org/t/dns-validation-for-lets-encrypt/139848>\
**Category:** Self-hosting\
**Created:** [27 בינואר,‏ 2020,‏ 4:00pm UTC](https://meta.discourse.org/t/dns-validation-for-lets-encrypt/139848 "2020-01-27T16:00:00Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![danb35](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@danb35](https://meta.discourse.org/u/danb35)\
**Post date:** [27 בינואר,‏ 2020,‏ 4:00pm UTC](https://meta.discourse.org/t/dns-validation-for-lets-encrypt/139848/1 "2020-01-27T16:00:00Z")

</div>

I’m wanting to install Discourse on a private network that won’t be accessible from the Internet, but I still want to set it up with Let’s Encrypt SSL. I’ve used DNS validation for a number of other hosts on this network, and it works well using either acme-dns (preferred) or Cloudflare’s DNS API. I can think of two possible ways to handle this:

- (preferred) Can the standard Docker container installation be configured to use DNS validation with Let’s Encrypt?

- If not, is there a way I can point the Discourse container to a cert/key somewhere in the filesystem, and cause it to reload when a new cert is generated?

---

_[View the full topic](https://meta.discourse.org/t/dns-validation-for-lets-encrypt/139848)._
