Activity log for bug #116066

Date Who What changed Old value New value Message
2007-05-21 21:02:07 demo360 bug added bug
2007-05-21 21:40:49 C de-Avillez ddclient: importance Undecided Medium
2007-05-21 21:40:49 C de-Avillez ddclient: assignee hggdh2
2007-05-21 21:40:49 C de-Avillez ddclient: statusexplanation @demo360: I cannot connect to members.dyndns.com either -- it times out. It looks more like they are indeed down.
2007-05-21 22:00:06 Marco Rodrigues marked as duplicate 60159
2007-05-21 22:10:41 C de-Avillez ddclient: assignee hggdh2
2007-05-21 22:10:41 C de-Avillez ddclient: statusexplanation @demo360: I cannot connect to members.dyndns.com either -- it times out. It looks more like they are indeed down.
2007-05-21 23:45:19 C de-Avillez removed duplicate marker 60159
2007-05-21 23:51:55 C de-Avillez ddclient: assignee hggdh2
2007-05-22 02:08:17 C de-Avillez ddclient: status Unconfirmed Confirmed
2007-05-22 02:08:17 C de-Avillez ddclient: importance Medium Low
2007-05-22 02:08:17 C de-Avillez ddclient: statusexplanation Indeed. http://www.dyndns.com/developers/specs/syntax.html states one must hit http://members/dyndns.org. I wonder when this has changed. Now... to http://ddclient.sf.net... sf.net states that Ubuntu users should report issues to us. So... I guess there is no need to open an upstream here. Issue: ddclient setup should suggest 'members.dyndns.org' instead of 'members.dyndns.com'. Although there seems to be a .com, it does not answer to the update requests; moreover, the first link in this comment states one should hit 'members.dyndns.org'. Seems pretty easy, and I will try to prepare a patch as soon as I can. Right now... thunderstorms are hitting north Texas, and I will stop playing on the laptop.
2007-05-22 02:08:17 C de-Avillez ddclient: assignee hggdh2
2007-06-16 21:50:03 Marco Rodrigues ddclient: assignee gothicx
2007-06-16 21:50:03 Marco Rodrigues ddclient: statusexplanation 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).
2007-06-16 21:50:51 Marco Rodrigues ddclient: status Confirmed In Progress
2007-06-16 23:03:05 Marco Rodrigues ddclient: status In Progress Fix Released
2007-08-17 10:44:36 Marco Rodrigues ddclient: status Fix Released Fix Committed
2007-08-17 10:44:36 Marco Rodrigues ddclient: statusexplanation It will be fixed on version 3.7.3 at Gutsy. Maybe after that a Backport for Feisty will be nice.
2007-10-08 15:04:10 Marco Rodrigues ddclient: status Fix Committed Fix Released
2007-10-20 14:10:55 PhobosK bug added attachment 'ddclient-bug.txt' (ddclient-bug.txt)
2007-10-25 16:59:54 PhobosK bug added attachment 'ddclient.patch' (Sets default value of the timeout option to the minimum one of 120 s)
2010-02-21 08:42:17 Launchpad Janitor branch linked lp:ubuntu/ddclient