#1038247 ddclient detects correct IPv6 address, but fails updating it

Package:
ddclient
Source:
ddclient
Submitter:
Paul Leiber
Date:
2026-02-08 20:35:01 UTC
Severity:
normal
Tags:
#1038247#5
Date:
2023-06-16 18:33:36 UTC
From:
To:
Dear Maintainer,

ddclient doesn't update my IPv6 address. It doesn't matter which option
(I tried ifv6, webv6) for detecting the IPv6 addess I use, both detect
the correct IPv6, but it doesn't get passed on to the DynDNS provider.
IPv4 seems to be working normally.

In verbose output, a line seems to indicate an error in line 2160 (the
same line is missing in a working setup):
---snip---
DEBUG:    nic_dyndns2_update -------------------
Use of uninitialized value $_[0] in sprintf at /usr/bin/ddclient line 2160.
INFO:     setting IP address to  for xxx
UPDATE:   updating xxx
DEBUG:    proxy    = <undefined>
DEBUG:    protocol = http
DEBUG:    server   = dyndns.strato.com
DEBUG:    url      = nic/update?<redacted>
DEBUG:    ip ver   =
CONNECT:  dyndns.strato.com
CONNECTED:  using HTTP
SENDING:  GET /nic/update?system=dyndns&hostname=xxx&myip= HTTP/1.1
---snip---

The last entry seems to indicate that no IP is sent. In a working
configuration, an IP is added to the line after myip=.

When replacing /usr/bin/ddclient with the current version of ddclient.in
from https://github.com/ddclient/ddclient, ddclient seems to be working
correctly (after adjusting the version check and the config location).

My ddclient.conf:

protocol=dyndns2
use=no
usev6=if, ifv6=enX0
login=xxx
password='xxx'
server=dyndns.strato.com
xxx

Best regards,

Paul

#1038247#10
Date:
2024-06-10 14:34:43 UTC
From:
To:
I have taken a snapshot of git some moths ago (February or march)
and it does work with both IPV4 and IPV6 at the same time.

Installed the original package and then did dh_autoreconf and other
stuff to build the new package after copying debian directory from
original package. NB: patches series do not apply and are not really
needed (touch for some missing file like NEWS is enough).

Time to package a git version (anyway 3.10.0 is several version behind
upstream last version).

#1038247#15
Date:
2026-02-08 20:26:48 UTC
From:
To:
After a couple of days of testing, it seems that this bug doesn't exist
anymore in the current stable package (3.11.2-2 on Trixie). I think this
bug can be closed.

Paul