SSL stopped renewing for me. I get
[09:17:15] INFO: Get domain ID
[09:17:15] INFO: Creating TXT record.
[09:17:15] ERROR: Could not add TXT record.
ERROR: deploy_challenge hook returned with non-zero exit code
I figured it out. I have a free DYNU account and they limit the number of DNS records and the plugin couldn’t add the TXT record.
DuckDNS seems to be really unstable for us, so Iam looking for an alternative. So this is still working, yeah?
And I saw the MultiDDNS add-on, anyone else here is using and happy? (saw one reponse in this thread)
Is there a way to use ONLY Dynu? It keeps asking for a Duck token…
Thanks @koying for this add-on!
I have replaced DuckDNS add-on with your Dynu DNS add-on to try to solve the “Google Home cannot reach Home Assistant” message and, so far, it is working perfectly with the bonus that Google Home’s reply and action are much… MUCH faster!!! This add-on deserves more attention and love from the community! 
For people switching to this add-on, consider the following additional steps:
Hi, I have some problems here. I’m trying to switch from DuckDNS, the problem is that when I access from Dynu DNS address the browser alerts that the SSL certificate’s name is not aligned with the website, and if I see the certificate details it still has the DuckDNS url in it.
The result is that I could tell the browser to ignore it and trust the certificate, but the Home Assistant Companion App can’t do that and it returns a URL error.
Should I do something else to properly switch from DuckDNS? Should I do some sort of reset of my SSL certificate in Let’s Encrypt? Why the browser still sees the DuckDNS certificate?
Thank you
I have problems updating dns name if router connection drops and comes back online do you find?