[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] IP Change
- Subject: RE: [cobalt-users] IP Change
- From: <rpaiz@xxxxxxxxxxxxxx>
- Date: Tue Mar 27 01:51:26 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> I had a number of sites using the same IP address. As the
> servers main site is now using SSL, I am changing the IP
> addresses for all the other sites.
Just to make sure... you're aware that you can only have one SSL-enabled
site per IP, but that this site *can* share the IP with lots of
non-SSL-enabled sites? The SSL site must be the only SSL-secured site on
the IP, but it doesn't have to be *the only site* on the IP.
> but could I have done anything different?
Yes.
> Would adjusting the time settings in the SOA for the
> sites with the new IPs have helped speed things up any?
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.
> Should I reboot the server or perhaps restart the
> server with (RaQ 4)
> /etc/rc.d/init.d/httpd stop
> /etc/rc.d/init.d/httpd start
If you've made any changes to the httpd.conf file, you should restart
the *web* server... not the machine itself.
--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>