[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] home site
- Subject: Re: [cobalt-users] home site
- From: elmer@xxxxxxxxxxxxxx
- Date: Fri Feb 23 23:27:45 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Sat, 24 Feb 2001, baltimoremd@xxxxxxxxxxxxxxx wrote:
} Can I/Should I move the contents to /home/sites/home and assign
} that domain to the first of the 3 IPS numbers in use.
My first rule is, if it ain't broke don't try fixing it.
Though it sounds as if you may be wasting an IP address or two, if
that is not an issue than, if it were my server, my first rule would
apply. Fact is, regardless of whatever considerations I may have,
or the nuances of the situation in question, if I don't absolutely
have to do it then my first rule applies.
Rule 2 is check rule 1 before doing anything.
No, I'm not joking or trying to make you laugh. There are
issues involved with swapping IP addresses on live sites. Nothing
that cannot be easily handled - I do it here an average of two or
three times a week and nobody ever notices. But significant downtime
can and will result when IP addresses on live sites are changed
without first shortening the TTL on the domains zone file.
While none of this is complex to do and you certainly should
learn how to do it, rule 1 still applies. A wise system admin
doesn't fix things that don't need fixing. Why take a chance on
breaking something (trust me, it happens even to the best of them)
if you don't have to?