rrthomas / ddclient Goto Github PK

Currently broken.

The original project at https://github.com/ddclient/ddclient has been archived, so those of us offering to take it over can no longer discuss things on its issue tracker.

As mentioned in ddclient#528 (comment) I am happy to take on the project. Since upstream has now been discontinued, I will definitely maintain the project for my own use short-term. If there's sufficient interest from e.g. packagers and collaborators, I'll be happy to maintain it longer-term too.

Why use my fork? I don't have particular expertise in DNS, but I'm a long-term user of ddclient, and I have a history of taking other unmaintained projects and maintaining them for a long time, e.g.:

• https://github.com/AbiWord/enchant
• https://github.com/rrthomas/recode
• https://github.com/rrthomas/mmv

The previous maintainer of ddclient rightly pointed out that the code base is not in a great state, and recommended that others use a different dynamic DNS client, so why continue with ddclient?

• Because it's familiar
• Because it supports a huge range of dynamic DNS providers.

Others have suggested rewriting ddclient in a more modern language than Perl. I sympathise with this aim; indeed, I have rewritten other projects that I have taken on, but I don't think it's a great idea for ddclient; at least, I don't have the time. Instead, if I find there is interest in my fork, I plan to make some radical simplifications to make ddclient more maintainable long-term:

• Remove support for finding IP address via many different routers. Quite simply, because I have never needed this myself.
• Remove duplicate support for internet communication: use curl, rather than WWW::Curl::Easy or the non-Curl code.
• Remove out-of-date/duplicate providers.

In general, I will concentrate on the core functionality of updating dynamic DNS entries, and tend to remove everything else, while retaining backwards compatibility on the command-line and in config files. In short, I will try to keep things working as well as I can for existing users.

A quick backwards-compatible release with essential bug-fixes and functionality enhancements only. To-do list:

• Fix caching problems (#3)
• Update changelog
• Contact downstream package maintainers? (Change of maintainers, change of curl dependency to be required, ...)
• Merge back into the original repo
• Set up signed tags (and commits)

regfishde seems to have broken ipv6 support thanks to deleting $config{$hash}{wantip} twice:

The cache logic has a bug causing ddclient to spam updates every refresh cycle.
For some users this caused bans from DDNS providers

See:

• ddclient#544
• ddclient#511
  Main issue is unrelated (see comments below), comments tbd
• ddclient#481
• ddclient#431

Some providers have improper implementations with regards to caching. It seems that these implementations never did right in the first place.

These fixes are not required for the v3.11 release, that is handled in #10 .

Providers without proper cache parameter implementation:

• 1984
• Njalla
• nsupdate