# How to secure Dynamic DNS

**URL:** <https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816>\
**Category:** Help\
**Created:** [March 4, 2019, 10:46pm UTC](https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816 "2019-03-04T22:46:31Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [March 5, 2019, 9:23pm UTC](https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816/19 "2019-03-05T21:23:15Z")

</div>

I can't advise you on using Boost - there's other forums and mailing lists for that.

> [@DragonOsman](#):
>
> And since this is a hand-made server basically, how do I automate the cert renewal for it?

The usual thing to do in production environments is to use a reverse proxy to handle SSL for you. That way, you do not need to worry about the implementation details of SSL and just use regular TCP/HTTP/whatever.

Common choices are nginx, Apache, etc ... though they are largely oriented around Linux.

Caddy has [releases for Windows](https://github.com/mholt/caddy/releases) which actually handles acquiring (and renewing), using the certificates for you .. you just [tell it to proxy to your application](https://caddyserver.com/docs/proxy).

---

_[View the full topic](https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816)._