Your favorite dynDNS clients?

Question

Howdy,
I'm setting up a dynDNS client, but want to know which ones you prefer or have had experience with.  Also, I currently do not see any dynDNS clients listed in Arch repositories (or maybe my keyword search just wasn't good enough).
Anyway, here's a few one's I've seen from dynDNS.org:
ddclient
JIP Update
RunDNS
DNS Update
ipcheck
UpdateDD
* I think I like the JIP Update client (with extensions) the best from what I've read.
Anyone have any experiences setting up a dynDNS client on linux? If so, here's basically what I'm looking for:
I have a T3 connection at my residence, and although I will be running several servers off my local machine, I would like to be able to "throttle" bandwidth usage coming in to my IP (in case of heavy loads), so as not to piss off my ISP.
Any suggestions?
thx.

Answer 1

For the most part, I figured it out.
Some notes:
1. The sample "ddclient.conf" file seems out of date.  For more accurate usage, you can type "ddclient --help".  But, in my case I had to dig a little deeper in the actual perl program.  In my case, it was a "simple" matter of using wrong delimitters (such as "", ",", and whitespace).
2. In my "special" case, since I do not use wildcards for both hosts (but only on one) and also for some other options unique to each host, I had to format my config file as such:
protocol=dyndns2,
login=loginname,
password=password,
wildcard=yes,
otheroptions=...,
myhost.homeip.net
protocol=dyndns2,
login=loginname,
password=password,
wildcard=no,
otheroptions=...,
myhost.dyndns.org
* Basically, you need at least two separate entries for each host.  You can combine all the entries together (separated by commas) and have the last line like "myhost.homeip.net myhost.dyndns.org" if you need to update multiple hosts, IF AND ONLY IF both hosts share the same settings, like MX, wildcards, etc.  In my case, they do not. 
** Moreover, you must begin each entry with the protocol option first.  If no "server=" option is specified, it defaults to "members.dyndns.org".  It will also use some other defaults if not explicitly stated.  But, the key was to start each entry with "protocol=", and not "server=".
Weird, but it works fine.  My usage of dyndns service may be unique, but if you need the customization for each host like i did, this is how you would do it.  Hope it helps.