Hey!
I’m just now noticing an issue: my ddclient configuration looks like this:
# This file can be used as a template for configFile or is automatically generated by Nix options.
cache=/var/lib/ddclient/ddclient.cache
foreground=YES
usev4=cmdv4, cmdv4='/nix/store/[...]-curl-8.12.1-bin/bin/curl https://checkipv4.dedyn.io/'
usev6=disabled
login=[hostname]
password=@password_placeholder@
protocol=dyndns2
server=update.dedyn.io
ssl=yes
wildcard=YES
quiet=no
verbose=no
[hostname]
However, whenever the ipv4 changed, dedyn.io seems to automatically add an ipv6 to my hostname, probably due to the automatic determination described here: IP Update API — deSEC DNS API documentation
I also tried with the following configuration:
# This file can be used as a template for configFile or is automatically generated by Nix options.
cache=/var/lib/ddclient/ddclient.cache
foreground=YES
usev4=cmdv4, cmdv4='/nix/store/[...]-curl-8.12.1-bin/bin/curl https://checkipv4.dedyn.io/'
usev6=ipv6, ipv6=''
login=[host]
password=@password_placeholder@
protocol=dyndns2
server=update.dedyn.io
ssl=yes
wildcard=YES
quiet=no
verbose=no
[host]
But then ddclient fails with:
WARNING: [host][usev6=ipv6 ipv6=<undefined>]> not a valid IPv6 address
WARNING: [host][usev6=ipv6 ipv6=<undefined>]> did not find an IPv6 address
WARNING: [host]> unable to determine IPv6 address with strategy '--usev6=ipv6'
And then dedyn.io still adds an ipv6.
Do you know how I could actually disable the automatic ipv6 setting using newer versions of ddclient?
I also tried setting the host to update.dedyn.io&myipv6= as suggested in the desec docs, but then ddclient complains that https://update.dedyn.io&myipv6= is not a valid url. And trying with update.dedyn.io?myipv6= with usev6=disabled still also leads to an ipv6 being added to my hostname.
Do you know what the good way to not have any ipv6 set for my hostname is, with newer ddclient versions?
This is my last issue with desec, and I think I’m this close to a perfect setup! I already recommended your system to a few friends 