On Jan 7, 2009, at 11:28 AM, LuKreme wrote: > On 7-Jan-2009, at 09:12, Jared Earle wrote: >> On 7 Jan 2009, at 16:09, LuKreme wrote: >>> Right, if you don't have the dyndns updater tool installed to update >>> the IP, then you need something else (like ddclient) to update >>> dyndns.org when the IP changes. All ddclient is is a CLI >>> replacement >>> for the dyndns updater utility. I'd go with the updater myself, >>> since >>> this is an OS X system. >> >> Yeah, but he specifically said "without using a GUI tool" > > Well, it's only a GUI tool the first time you use it. After that it > is a background daemon that you never even look at. I think it's been > two years since I launch DynDNS Updater.app > > > --
OK Thanks folks. I'll use DynDNS custom service with their updater client for OS X. Forget about running my own name server. If I had more time, maybe it'd be fun, but right now I'm working full- tilt on a new book and I really don't have the time to play. I appreciate all the feedback. So, to recap, this will work, right? --DynDNS Custom, using their name servers and their mx. --Use their updater to deal with my dynamic IP. --And I don't need to do anything special behind the Airport router? Jeff _______________________________________________ OSX-Nutters mailing list | [email protected] http://lists.tit-wank.com/mailman/listinfo/osx-nutters List hosted at http://cat5.org/
