public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: 5p9 <5p9@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Introducing DDNS
Date: Wed, 25 Jun 2014 19:20:36 +0200	[thread overview]
Message-ID: <53AB04E4.5090602@ipfire.org> (raw)
In-Reply-To: <1403691707.12463.90.camel@rice-oxley.tremer.info>

[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]

Hi Michael & Stefan,

thanks for your Work! Looking forward to the first test with the new
feature :)

Best,
Thomas

Am 25.06.2014 12:21, schrieb Michael Tremer:
> Hello,
> 
> this is a post to update you all about the recent developments regarding
> the support for the various upcoming dynamic DNS providers.
> 
> 
> Rationale
> 
> Some of the major dynamic DNS providers stopped their free services or
> made them unusable so that people started searching for alternatives. In
> IPFire 2, a script called setddns.pl [1] is responsible for updating the
> dynamic DNS records. This script has grown over the last couple of
> months and if you have looked into it you will have noticed that it has
> become from ugly to almost un-maintainable. The decision that we don't
> want to take this mess with us into the next generation of IPFire was
> already made many years ago.
> 
> 
> DDNS
> 
> A project called ddns was started which is a pure Python client that is
> much more flexible, cleanly rewritten and easily extensible. It is
> cross-platform, cross-distribution and does not need any third-party
> python modules.
> 
> The basics already written years ago, Stefan Schantl and I worked on
> making this ready for IPFire 2 and added all the providers that are
> currently supported by setddns.pl and ez-ipupdate.
> 
> The source for the new DDNS tool can be found over here:
> 
>   http://git.ipfire.org/?p=ddns.git;a=summary
> 
> or on GitHub
> 
>   https://github.com/ipfire/ddns
> 
> were you can send us pull requests for supporting new providers and so
> on.
> 
> Bug reports go to the usual place:
> 
>   https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
> 
> There is no fixed release schedule for this, but we are pretty sure that
> this won't take long until DDNS arrives in IPFire 2. That means that we
> won't take any patches for the setddns.pl script that add support for
> new providers any more.
> 
> We appreciate any contribution and as always hope to get some feedback
> back from the community!
> 
> Best,
> -Michael
> 
> [1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e77fce5c024a3f17ba4c892a94abfe95845e8c6;hb=HEAD
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
> 

  parent reply	other threads:[~2014-06-25 17:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 10:21 Michael Tremer
2014-06-25 14:53 ` R. W. Rodolico
2014-06-25 17:20 ` 5p9 [this message]
2016-06-07 13:22   ` SPDNS DDNS Update 5p9
2016-06-07 14:24     ` Michael Tremer
2016-06-07 14:28       ` 5p9
2016-06-07 14:35         ` Michael Tremer
2016-06-07 14:38           ` 5p9
2016-06-07 14:39             ` Michael Tremer
2016-06-20 14:58               ` Michael Tremer
2016-06-21 10:40                 ` Stefan Schantl
     [not found] <1404155136.5242.3.camel@hughes.tremer.info>
2014-07-09 17:37 ` Introducing DDNS Stefan Schantl
2014-07-09 18:30   ` Michael Tremer
     [not found] <CAEVn7dmfC5dSRrRoad+TDXODfcEPUtjYVd5rbCzsN50u_6-vvA@mail.gmail.com>
2014-07-09 18:31 ` Michael Tremer
2014-07-10 13:34   ` Arne Fitzenreiter
2014-07-10 15:09     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53AB04E4.5090602@ipfire.org \
    --to=5p9@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox