Add-on: Dynu DNS (alternative to DuckDNS)

Installation Home Assistant OS
,
#1

As DuckDNS is a bit shaky recently, I created an alternative add-on using the Dynu DNS provider, which ranks as amongst the best free dynamic DNS providers around as far as I could see.
It has a bit more variety as far as the root domains available, which is nice.

The addon is at 99% a copy of the duckdns addon.

Disclaimer:
I don’t use the add-on myself. My “main” HA is not even on HassOS, tbh.
This is a “gift” to the community, and an exercise for myself.

About

Dynu DNS is a free service that points a DNS to an IP of your choice. This add-on includes support for Let’s Encrypt and automatically creates and renews your certificates. You need to sign up for a Dynu DNS account before using this add-on.

Installation

  1. Navigate in your Home Assistant frontend to Supervisor → Add-on Store.
  2. Click 3-dots menu at upper right > Repositories and add this repository URL: https://github.com/koying/ha-addons
  3. Scroll down the page to find the new repository “Add-ons from Koying”, and click one of the new add-ons.
  4. Click Install and give it a few minutes to finish downloading.
  5. Configure at Configuration tab or separate file in Configuration folder according to the instructions of the add-on.
  6. Click Start, give it a few dozen seconds to spin up.
  7. Enjoy.

Issues?

Open a ticket at the github repository

3 Likes
DuckDNs down again, Alternate to Duckdns
Deceptive Site Ahead after switching to DuckDNS
ISP Blocking Port 80 SSL Certificate Solution
#2

Thanks for this!, I use Dynu and installed the LetsEncrypt add-on and then found it is not one of the supported DNS providers, this is just what I needed, will give it a try…

#3

I tried duckDNS and it was highly unstable. This works perfectly! thank you

#4

I have been using Dynu for years now for my entire network of subdomains and it was amazing service. its a shame that entire HA community is endorsing duckdns as the configuration options on Dynu are even wider.

Now I have one question, the duckDNS addon is taking care of the letsencrypt generaiton as well is it part of this one too ?

#5

Yes, it does

#6

I uses Let’s Encrycpt in Nginx proxy so it’s as disabled on Dynu DNS AddOn.
But I have a problem to run Dyny DNS updater for my domain.

Idea to solve this?

#7

No clue. Just tried with letsencrypt disabled and it worked fine for me.

#8

Hmm… Ok, I have to try to debug the script or write one more alternative. :smiley:

It seems to be Dynu problem. IP update for another domain works. I made the support ticket for Dynu about this.

#9

Hi,

I just tried to install this and seems my subdomain IP isnt updating. I see the bellow in addon log:

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Using main config file /data/workdir/config
Account already registered!
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

and one line in HA logs:
2022-02-15 16:32:28 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/4e8751bd_dynudns/stats - Container addon_4e8751bd_dynudns is not running

Any ideas?

#10

Well the container is not runing. Try restarting the addon from the supervisor. if it still show the same error it may mean that you either run out of space or something else is colliding with that container.

#11

DuckDNS is down again, no connection with google home. So I want to try this addon.
Is there a manual for how to set this up?
I have made an account at DynuDNS and installed the addon.
How do I get the pem-files?

#12

DuckDNS down again, so I installed DynuDNS. Works perfect with the browser, however on my Android phone with the Home Assistant App I get the message: not possible to connect with Home Assistant. Certificate is not right, check the certificate … etc.

How can I solve this issue, or does the App only works with DuckDNS?

#13

Thanks @koying, cool you built this without even needing it! ha
Think the pull requests need a quick review, seems like @zerocritical has fixed some issues that have appeared since you originally wrote it. Either that or maybe zero could do a fork or go admin if he’s actively using it?

I used dynu for many many years now… no issues like I’ve had with duckdns (not hating it was great due to its ease and being free, but this addon now makes dynu as easy to use).

1 Like
#14

Hi all, I have HA core installation, how can I use let’s encrypt?

#15

@koying hello, can i use it together with duckdns and have both? and also have both certificates? thank you

#17

Works great. Thanks!
My Duckdns URL kept getting banned by Google. Hopefully, this doesn’t get banned.

#18

Does anyone know what this error means. I uninstalled duckdns and installed dynu via the instructions provided. it worked last night but this morning i couldn’t access it. When i try to start it I get the error below and it just stops.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
# INFO: Using main config file /data/workdir/config
+ Account already registered!
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
#19

UPDATE: Since Update to 2023.05.03 it is working again.

I do not know why, but since a few days HAOS is not reachable with Dynu. SSL certificates are all ok and the only thing I did was to install the official updates on HAOS. Btw Duckdns still works but in the past both worked for me at the same time… Anyone an idea?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[06:54:39] INFO: Renew certificate for domains: xxx.ddnsfree.com and aliases: 
# INFO: Using main config file /data/workdir/config
Processing xxx.ddnsfree.com
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Aug 12 09:37:11 2023 GMT (Longer than 30 days). Skipping renew!
#20

Does this also update the IP address at DYNU if it changes?

#21

What the token field for? Is it the API-Key?