Mar 192009

I have some minor sites run­ning on the base­ment OpenSol­ar­is box, and since our IP address changes reg­u­larly, I use ddcli­ent to noti­fy DynDNS of the changes. It was work­ing just fine on the old Debi­an box, but of course OpenSol­ar­is does things dif­fer­ently, and the ddcli­ent pack­age doesn’t come with all the bits you need to make it work.

Step one: down­load the ddcli­ent pack­age from Source­forge, and fol­low the instruc­tions in the README as to where to install it. Easy enough, done.

Step two: go to the DynDNS site, log in to the account, go to the Sup­port Tools sec­tion of the web­site, and click on the “Update Cli­ent Con­fig­ur­at­or”. This takes you to a page that will auto­mat­ic­ally gen­er­ate the con­fig­ur­a­tion file for ddcli­ent for your account. This is one of the reas­ons I like DynDNS, by the way, they think of little use­ful tools like this. 

Step three: make the con­fig­ur­a­tion changes in the ddclient.conf file, and try run­ning the ddcli­ent Perl script to see if it works, using ddclient -daemon=0 -debug -verbose -noquiet to get all the error mes­sages. One tip: if you have spaces in your pass­word, sur­round it with single quotes, not double quotes. The lat­ter don’t work.

Step four: the hardest for someone new to OpenSol­ar­is is to fig­ure out how to run the dae­mon. It turns out that Sol­ar­is has a “Ser­vices Man­age­ment Facil­ity” (SMF). The spe­cific instruc­tions to fol­low, once you’ve figured out the basic con­cepts, are at Chris Gerhard’s ddcli­ent meets SMF. Mind you, I did need to read the doc­u­ment­a­tion on Man­aging Ser­vices to find out where to put the file (/var/svc/manifest). Just as well Sun lets lots of people blog, it cer­tainly makes it easi­er to find inform­a­tion. I do wish they could fig­ure out how to give their stand­ard doc­u­ment­a­tion mem­or­able URIs though.

Now I just have to wait until our loc­al IP address changes to see if it works. [Update: yup, it works.]