Re: [cobalt-users] IP Change

["Cobalt-Canada" <info@xxxxxxxxxxxxxxxxx>]

----- Original Message -----
From: <rpaiz@xxxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Tuesday, March 27, 2001 9:29 AM
Subject: RE: [cobalt-users] IP Change


> > (edited) I am changing the IPs for a number of sites...
> > Would adjusting the time settings in the SOA for the
> > sites with the new IPs have helped speed things up any?
> Arthur
>
> Yes. Set the TTL values to something low (like 1 hour) and leave them
> that way for several days. Then change the DNS to the new addresses and
> return the TTL to a normal value. Hopefully most people respect caching
> limits and hopefully many people don't even notice. Those that don't
> respect expire times, or those that queried your DNS within the last
> hour, will see the site as down until they refresh their DNS.
> Rudolfo

Hi Rudolfo

Thanks for the reply. Should I be setting the time to live value low just
for the sites that are having the IP addresses changed, or can I get away
with just changing the TTL for the name server itself? (I think John Troher
may have answered this... his reply [thanks, John] was "change the TTL on
the hosts we are going to change to 5 minutes  for 24 hours...")

When I say ask if I can just change the "name server" I might not be using
the correct terminology. I am referring to the TTL setting I see when I go
to "control panel - DNS parameters" and then clicking on the IP
xxx.xxx.xxx.0/24 - I assume this is the "network" referred to when it says
"select domain or network." There is a SOA configuration there as well as
for the one I see just for domains in question themselves...  the ones that
are were getting the new IPs.

As you mentioned, this may be a waste of time as many virtual sites should
be able to share an IP even though one of the sites using it has SSL. Again,
this all started when I had a client comment about "warnings about the
certificate" when they had clients fill out forms on their site.

Thanks - Arthur