ddns/deSEC setup issue

dynDNS at dedyn.io
1

Hello, I was hoping someone might be able to point out the step I am missing or what I am doing wrong.

Setup: DNS hosting for my domain (example.com) is on deSEC using deSEC name servers

I created an A record for vpn.example.com in deSEC

I have a pi4 running pivpn at my home which has a dynamic IP from the ISP

I am also running ddclient on my pi4 with the following setup:

Provider: other

Protocol: dydns2

Server: update.dedyn.io

proxy: none/blank

user name: vpn.example.com

password: token from deSEC

ip discovery: web based / checkip.dns.he.net

time: 5m

host to update: vpn.example.com

But this setup doesn’t work, my ip does not get updated with deSEC – where am I going wrong?

2

Hello @redacted,

Are there any warnings or errors being reported or logged by your dyndns2 client?

3

@Bruce5051: In case you haven’t guessed I’m a bit of an amateur, but when I use the command “sudo ddclient -force” it produces no errors.

This is my config file:

# /etc/ddclient.conf

protocol=dyndns2 \
use=web, web=he \
server=update.dedyn.io \
login=vpn.exmple.com \
password=‘zo4XWmmPkXUs___zmKPJWpFkpXrZ’ \
vpn.example.com

This is what I get with debug:

DEBUG: proxy =
DEBUG: protocol = https
DEBUG: server = checkip.dns.he.net
DEBUG: url =
DEBUG: ip ver =
DEBUG: get_ip: using web, https://checkip.dns.he.net/ reports 206.XX.XX.XXX
WARNING: skipping update of vpn.example.com from to 206.XX.XX.XXX.
WARNING: last updated but last attempt on Sun Aug 31 12:57:07 2025 failed.
WARNING: Wait at least 5 minutes between update attempts.

1 Like
4

Hi @redacted,

I am not an expert; I don’t really know the ddclient.
Kindly wait for more knowledgeable deSEC community volunteers to assist.

5

@redacted,

Please change the password immediately!

In the future please don’t post the actual password, this is a great case for using using the word redacted.

I made the quote say redacted so as to to reduces the visibility.

For password, I mean password and/or token.

6

Thats not the actual password/token or the real domain name — both have been changed to protect the innocent

thanks though

1 Like
7

Excellent @redacted, sorry for the alarm!
Have a pleasant day. :sun_with_face:

8

Hi @redacted,

the docs mention ssl=yes. Not sure it it’s really required or if that is ddclient’s default. But it certainly won’t hurt.

Also, make sure to use the token value. Not the token’s ID (a UUID). Not your deSEC account password. deSEC shows the value only once on token creation.

If that does not help, try getting a debug log with actual interaction with the deSEC update service. Either wait five minutes (and disable any ddclient background process/cron job) or somehow force ddclient to ignore the delay (not sure if it has an option).

1 Like
9

@black : that was the solution once I added ssl=yes to my config file its now working!

# /etc/ddclient.conf

protocol=dyndns2 \
use=web, web=he \
server=update.dedyn.io \
ssl=yes
login=vpn.exmple.com \
password=‘zo4XWmmPkXUs___zmKPJWpFkpXrZ’ \
vpn.example.com

Thank you so much for the help!

1 Like