I have several accounts, most are used for pushing backups over ssh to remote locations. The one problem with it is a change in IP might not register with the service for some time. I have had backups fail because the ISP changed the IP sometime just before the backup was to run.
That's not a frequent problem, and isn't a show stopper, for sure. I think DynDNS is an excellent solution, better than having cron running scripts on every remote host. Cron can fail, there might be a timeout with whatsmyip, there are variables that can render the whole thing useless.
DynDNS offers one point of failure, if you want to look at it that way, and they are redundant beyond belief. Your only real point of failure is if the remote host or firewall go down, eg power failure.
The point of the article was a how-to in the event one doesn't want to use a dynamic DNS solution. The only glitch I see is in my prior post: the command doesn't work for me using an rpm based distribution. (I'm pretty sure I'm not typing anything wrong)
Keep Up with TechRepublic