The only issue with that cron job is it only makes the connection once per day & your computer has to be on when it is scheduled to run.

This is absolutely true. However, it’s also the case that the vast majority of broadband connections change IP addresses rarely. I have used both DSL (SWBell) and Cable (Comcast) for many years and months go by without getting a new IP address. I understand that with dial-up, this is not the case and it may not be the case will all broadband suppliers.

I think it would be better to change the schedule to something like the following.
0 * * * *

That should work, unless Open DNS considers that spam (some dynamic IP sites consider it impolite to “update” your IP too often with the same address).

Or you could use the following article to use DDClient.

As I stated in my article, my Linux box is behind a firewall. That firewall always provides the Linux box the same IP address. DDClient doesn’t know what the internet facing address of the firewall is UNLESS you specifically configure it to hit an external web site (exactly the same way my example does). Unless DDClient hits that site on some kind of scheduled basis (like cron, maybe), it won’t know that the external address has changed. So, it’s a script doing pretty much the same thing my example is doing or it doesn’t work.

I think it would be better to change the schedule to something like the following.
0 * * * *

Then it runs once an hour which if your IP address changes at some time during the day you will not be updated.

Or you could use the following article to use DDClient.

http://www.opendns.com/support/article/192

Rev Room: http://www.reverbnation.com/rss/venue_shows_rss/revolutionmusicroomtherevroom

Sticky Fingerz:
http://www.reverbnation.com/rss/venue_shows/stickyfingerzrocknrollchickenshack