Bug 10556 - DDNS: "Dynu" service is not working anymore
Summary: DDNS: "Dynu" service is not working anymore
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Stefan Schantl
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-17 11:54 UTC by Stefan Ferstl
Modified: 2014-08-04 09:10 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Ferstl 2014-06-17 11:54:58 UTC 
Note: GitHub Pull Request #32 [1] solves this issue

The DDNS service "dynu.ca dyn.ee dynserv.(ca|org|net|com)" is not working anymore because it uses the URL http://dynserv.ca for the DNS updates. However, the dynserv.ca domain does not exist anymore. The Dynu service is now only reachable via the dynu.com domain. The API specification for DNS updates can be found under [2].

I would also suggest to change the name of the service in the web gui from "dynu.ca dyn.ee dynserv.(ca|org|net|com)" to simply "dynu.com" as the other domains don't seem to exist anymore, either. If this is OK, I can (try to) include that change in the Pull Request as well.

[1] https://github.com/ipfire/ipfire-2.x/pull/32
[2] http://www.dynu.com/Default.aspx?page=dnsapi
Comment 1 Stefan Schantl 2014-06-17 20:02:53 UTC 
Hallo Stefan,

your changes have been merged to the IPFire "next" repository and will be released with core update 80.

http://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=7eb25cb302c28a7969a160a8672df6744c0b85af

Thanks for your contribution,

-Stefan
Comment 3 Stefan Schantl 2014-08-04 09:10:31 UTC 
Fix released with IPFire 2.15 - Core 80.