Add-on: Dynu DNS (alternative to DuckDNS)

Installation Home Assistant OS
,
42

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.

43

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)

44

Is there a way to use ONLY Dynu? It keeps asking for a Duck token…

45

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! :slight_smile:

For people switching to this add-on, consider the following additional steps:

  1. If you have your own Google Home integration, you have to update your token/ integration settings to the new Dynu URL
  2. Your mobile app URL has to be updated with the new Dynu URL
46

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

47

I have problems updating dns name if router connection drops and comes back online do you find?

48

I’m hoping someone can help me. I have been playing around to get this working so I screwed up my HA. I did a full restore and I’m back on DuckDNS. I only have this installed and not using Lets Encrypt or DNSMasq or NGINX and it all works fine.

I then disabled my DuckDNS add-on, installed the Dynu DNS and configured it. Logs seem to be fine:

10:50:56] INFO: Initializing Dynu DNS Home Assistant Add-On for Domain(s): xxxxxx.ddnsfree.com

INFO: Using main config file /data/workdir/config

  • Generating account key…
  • Registering account key with ACME server…
  • Fetching account URL…
  • Done!
    [10:51:00] INFO: Entering main Dynu DNS loop
    [10:51:01] INFO: According to: https://ipv4.text.wtfismyip.com , IPv4 address is xxx.xxx.xxx.xxx
    [10:51:03] INFO: Getting current domain configuration for domain: xxxxxxxx.ddnsfree.com
    [10:51:04] INFO: - Dynu DNS get config Success. “statusCode”: 200
    [10:51:04] INFO: Updating Dynu DNS: xxxxxxx.ddnsfree.com IP addresses
    [10:51:05] INFO: - Dynu DNS IP update Success: statusCode: 200
    [10:51:05] INFO: Renew certificate for domains: xxxxxxxx.ddnsfree.com and aliases:

INFO: Using main config file /data/workdir/config

  • Creating chain cache directory /data/workdir/chains
    Processing xxxxxxxx.ddnsfree.com
  • Creating new directory /data/letsencrypt/xxxxxxxx.ddnsfree.com …
  • Signing domains…
  • Generating private key…
  • Generating signing request…
  • Requesting new certificate order from CA…
  • Received 1 authorizations URLs from the CA
  • Handling authorization for xxxxxxxx.ddnsfree.com
  • 1 pending challenge(s)
  • Deploying challenge tokens…
    [10:51:11] INFO: Get domain ID
    [10:51:11] INFO: Creating TXT record.
    [10:51:12] INFO: + Settling down for 10s…
  • Responding to challenge for xxxxxxxxx.ddnsfree.com authorization…
  • Challenge is valid!
  • Cleaning challenge tokens…
    [10:51:26] INFO: Get domain ID
    [10:51:27] INFO: Checking for TXT record.
    [10:51:27] INFO: Removing TXT record.
  • Requesting certificate…
  • Checking certificate…
  • Done!
  • Creating fullchain.pem…
  • Done!

I can access it from outside my network but I’m getting an HTTPS issue about the certificate. What am I missing

49

First, tell us the details about the actual certificate error (go to details)

50

make sure you stop, uninstall the duckdns addon, make sure you acceptterms option is set to true inside this plugin, restart hassio (or the plugin) to regenerate the cert. that should make it work

51

thanks for the addon!! You make my day. I was suffering for months with the annoying message about "cant reach " from Google Home and now works like a charm. Regards!!