Re: Introducing DDNS

["R. W. Rodolico" <rodo@dailydata.net>]

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

Because of this same issue, I created a ddns system a few years ago. I
also didn't like the possibility of DNS tracking the commercial dyndns
companies would be capable of. I simply got a new domain and set it up.

It is a combination of bash and perl. I have never written an article on
it or anything but I have some documentation. I'll be happy to write
some better documentation and comment the code a little so it can be
used when creating this new one.

Can't say much about it as it is fairly simple once I got the concepts
down. I chose to set it up more securely by using ssh keys for the
connection between the client and the dns server. Currently it is
implemented on all my IPFire routers as a simple cron job that runs
every hour.

Let me know if it might be helpful and/or if you need any help with
writing the new one.

Rod

On 06/25/2014 05:21 AM, Michael Tremer wrote:
> 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
> 

-- 
R. W. Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net