Now I am totally confused. The original ddclient 3.7.1 used 'members.dyndns.org', and the Ubuntu patch reset it to 'members.dyndns.com':
--- ddclient-3.7.1/ddclient.orig 2007-04-30 00:40:49.000000000 +0100 +++ ddclient-3.7.1/ddclient 2007-04-30 00:40:59.000000000 +0100 (snip) @@ -342,7 +342,7 @@ 'postscript' => setv(T_POSTS, 0, 0, 1, '', undef), }, 'service-common-defaults' => { - 'server' => setv(T_FQDNP, 1, 0, 1, 'members.dyndns.org', undef), + 'server' => setv(T_FQDNP, 1, 0, 1, 'members.dyndns.com', undef), (snip)
So... instead of preparing a patch I think my best option it to let this bug stay in confirmed status, so that the maintainer may look at it and decide on a course of action (either reverting the dyndns patch, or confirming it).
Now I am totally confused. The original ddclient 3.7.1 used 'members. dyndns. org', and the Ubuntu patch reset it to 'members. dyndns. com':
--- ddclient- 3.7.1/ddclient. orig 2007-04-30 00:40:49.000000000 +0100 3.7.1/ddclient 2007-04-30 00:40:59.000000000 +0100
'postscript' => setv(T_POSTS, 0, 0, 1, '', undef), common- defaults' => { dyndns. org', undef), dyndns. com', undef),
+++ ddclient-
(snip)
@@ -342,7 +342,7 @@
},
'service-
- 'server' => setv(T_FQDNP, 1, 0, 1, 'members.
+ 'server' => setv(T_FQDNP, 1, 0, 1, 'members.
(snip)
So... instead of preparing a patch I think my best option it to let this bug stay in confirmed status, so that the maintainer may look at it and decide on a course of action (either reverting the dyndns patch, or confirming it).