Ben, Thanks, belatedly, for your reply. This is a very useful perspective for me. I appreciate it.
Adam On 10/6/2009 7:37 PM, Ben Scott wrote: > On Tue, Oct 6, 2009 at 5:58 PM, Adam Greene <[email protected]> wrote: > >> We are considering suggesting dynamic DNS to associate his webserver domain >> name with the changing IP addresses. >> > > It works okay for what it is. It's a low-budget solution. If the > website is critical to business, I wouldn't recommend it. If the end > customer doesn't react well to "we found the problem but it's outside > of our control", avoid it. If it's just an informational site and not > a big deal, it's appropriate. > > It won't work for some small segment of your users. Exactly how > small varies. It's often an insignificant segment, but occasionally > is not. AOL used to ignore DNS TLL all the time, but I hear they've > gotten better (just in time to go out of business). > > How well it works is impacted by all sorts of things -- DNS > propagation delays, DNS caching, stale lookups, nameservers which > ignore your TTL, phase of the moon, etc. Diagnosing individual causes > is basically impossible, and even when you find a cause you generally > can't do anything about it. > > One problem is that many browsers (most?) only resolve a name once > and then keep that IP address in memory until you exit the browser. > This isn't a function of DNS but application design. > > Doom and gloom aside, dynamic DNS works very well in the general > case. You just have to be willing to accept its limitations. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
