On Sat, 29 Jan 2005, stuporglue wrote:
I've heard some people voice the opinion that dyndns was a "wrong" solution....it's not, I take it.
IM(NS)HO,
dyndns can often be the "wrong" long-term solution, but short-term it can be very handy. It's the perfect fit if you just want to shell into your home network but don't want to memorize your IP address every time it changes. It's even pretty good if you want other people to access your computer (http, ftp, etc).
It starts getting really clunky when you want to (a) set your computer up as an SMTP server (not so much because of dyndns's limitations, but simply because you're very likely get some spammer's ex-IP address when your IP address changes, and some people (like AOL?) drop email from dynamic IP addresses anyway) ... (b) basically do anything more complex than serving a few web pages to friends and the like.
I've been using dyndns on several boxes I have and it's really, really useful. However, if you want the box to be a "real" server, dyndns is probably not the way to go (having learned this from sad experience, but still trying to fight through it because stupid sbcglobal won't sell a single static IP address to home DSL users, but requires a business account with five IP addresses which is over twice as expensive).
Just my two cents about dyndns ... ~ Ross
--
This sentence would be seven words long if it were six words shorter.
--------------------
BYU Unix Users Group http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
