Duck DNS is a free service which will point a DNS (sub domains of to an IP of your choice. This add-on includes support for Let’s Encrypt and will automatically create and renew your certificates. You will need to sign up for a Duck DNS account before using this add-on.

  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  "token": "sdfj-2131023-dslfjsd-12321",
  "domains": [""],
  "seconds": 300

Configuration Variables



Let’s Encrypt is a free, automated, and open certificate authority.



If you accept the Let’s Encrypt Subscriber Agreement, it will generate and update Let’s Encrypt certificates for your DuckDNS domain.

Default value:




Your Duck DNS API key, from your DuckDNS account page.



A list of domains to update DNS.



Seconds between updates to Duck DNS.

Home Assistant configuration

Use the following configuration in Home Assistant to use the generated certificate:

  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

If you use a port other than 8123 or an SSL proxy, change the port number accordingly.

Router configuration

You’ll need to forward the port you listed in your configuration (8123 in the example above) on your router to your Home Assistant system. You can find guides on how to do this on Port Forward. Noting that you’ll only need to forward the TCP port.

Ensure that you allocate the Home Assistant system a fixed IP on your network before you configure port forwarding. You can do this either on the computer itself (see the install guide or via a static lease on your router.

Restart Home Assistant for the configured changes to take effect. When you access the Home Assistant frontend you will now need to use https, even when accessing local instances, for example at

Generate Let’s Encrypt certificate for Duck DNS sub sub domains

To generate certificates for update the domain JSON settings to:

  "domains": ["","*"],