Re: [cobalt-users] Adjusting TTL for domain change

[SM <nntp@xxxxxxxxx>]

At 22:16 08-09-2001 -0700, Jeff Lasman wrote:
>For most of us if our DNS server is done, so are our websites.  However
>the difference in the error message is important; if DNS is cached
>elsewhere, or you've got a good secondary elsewhere, then the user will
>read that the site is temporarily unreachable.  If your DNS wasn't
>cached anywhere, the user will read that the domain doesn't exist.  Big
>difference.

I don't think the admin of the secondary DNS would provide the service for
free if the server is being taxed as a primary.  DNS caching has spared me
some hassle a few times.  When I get "domain cannot be resolved", I don't
bother going to the site again.

At the end of the day, if you are running a low volume site, it doesn't
make matter if you are using a very low TTL.  I won't argue about best
practices. :)

Regards,
-sm