Dyndns for desec.io => something seems wrong

geolr · March 26, 2026, 8:20pm

Hi there,

likely the error sits in front of the keyboard...
I may very well do something wrong...

Device D-link DIR-878
OpenWrt 24.10.5

My goal:
Have my dyndns name with desec.io updated using the router.
There is another dyndns already present (noip) which works flawlessly.

I could update at desec.io using a curl-command. Thus, my account and credentials are functional. Dynamic name resolves after.

As DDNS Service provider I have selected desec.io
IPv4
Username = domainname to update, my dynamic hostname ending with .dedyn.io
Password = my token for the service
https: off or on seems to make no difference

From the log at /var/log/ddns/desec.log
I read
DDNS Provider answered: nohost
Which seems like the request asks for a dynamic name that is not defined.
The parameter for the username seems correct
/usr/bin/curl -RsS -o /var/run/ddns/desec.dat --stderr /var/run/ddns/desec.err --interface wan --noproxy '*' 'https://update.dedyn.io/update? username=something.dedyn.io&password=***PW***&hostname=update.dedyn.io&myipv4=1.2.3.4&myipv6=preserve'

I tried earlier with wget-ssl, to the same result.

Making a custom service with the update url update.dedyn.io, then the update works.
Still there is a XRH time-out error reported.
In the log it says for the answer ...301 Moved permanently...
And Forced update successful

Any input if this is OK now?

Many thanks!

edit: The docs at desec:

editedit:
should this maybe get updated?

github.com/openwrt/packages

net/ddns-scripts/files/usr/share/ddns/default/desec.io.json

master

{
	"name": "desec.io",
	"ipv4": {
		"url": "https://update.dedyn.io/update?username=[USERNAME]&password=[PASSWORD]&hostname=[DOMAIN]&myipv4=[IP]&myipv6=preserve",
		"answer": "good|nochg"
	},
	"ipv6": {
		"url": "https://update.dedyn.io/update?username=[USERNAME]&password=[PASSWORD]&hostname=[DOMAIN]&myipv6=[IP]&myipv4=preserve",
		"answer": "good|nochg"
	}
}

AndrewZ · March 26, 2026, 8:34pm

Make sure you have only one DDNS provider active (with non-custom configration) then restart the service and show the recent DDNS client log. See this as an example.

geolr · March 26, 2026, 8:48pm

right, good point.
I disabled the other service, created a new based on the predefined desec.io
This has worked.

Thus, I guess resolved.
Maybe pending to find out if the config should be updated (last edit in github 3y ago)

Thanks!

And Everyone: Very happy to be able to keep running my old hardware with current OpenWRT!
Thank you!