|
I wrote a simple DynDNS update client. It is a bash script and will run on Linux computers, and probably will run just fine on Mac OS X, too. I was getting tired of monolithic, complex, not necessarily working clients for Linux. It has very little configuration and very few options (zero, actually). You just configure it with your account details, and then run it from cron. I have only tested it on Ubuntu, and it still needs some polish (like sanity checking for required dependencies or internet connectedness). But it is very easy to set up and it works. Any thoughts? Thanks |
|
Hi, I hope you read the DynDNS protocol requirements. There are at least two important requirements for an updater: It MUST NOT send update requests when the host already is updated. And - at least officially - it MUST keep a persistent state info surviving a reboot. The second requirement is something I did not wish to implement in "rxdyndns", a simple update client vintage 2005 for OS/2 warp, and therefore I never submitted it to the formal audit for "official" update clients. Yeah, I saw their API and specs and I'm confident that my little thing does both. Thanks
Jan 31 at 08:18 PM
JDS
|
|
These documents are the requirements Frank referred to. Assuming you've followed them you share it the same way any open source package is shared. That means word of mouth, blog posts etc. You'll also want to build RPM and DEB packages for the major distributions to encourage people to try it. One thing not covered in the documentation is that you do need to push an update about ever 28 to 30 days, regardless of whether or not the IP changed, to avoid account inactivity expiry. |
