Latest versions of DuckDNS doesn't include several domains as additional DNS in certificate. Update: v1.24 solves the problem

jjaammhh · August 12, 2025, 6:30pm

I have 2 subdomains configured in my DuckDNS account. And also configured in my DuckDNS addon.

Typically, this has been working flawlessly, until recently, after one of the latest recent updates in the addon.

Now only the first domain is included in the certificate under the DNS section.

Just to clarify, I’m not talking about aliases, but about 2 different DuckDNS subdomains

Using Home Assistant OS core-2025.8.1, with DuckDNS addon 1.23.0

jjaammhh · August 13, 2025, 9:47am

Updating DuckDNS addon to v1.24 solves the problem. A HA reboot is required after.

wunsch · August 20, 2025, 3:51pm

I am on DuckDNS v1.26.

I have multiple ALIASs configured, but only the last one makes it onto the certificate.

That is very limiting.

Does anyone know a way around that?

My config (anonymized):

Logs (I only have the restart logs right now - the creation of the certificate was about 2 hours ago, and they are gone, I think):