Re: [cobalt-users] moving primary nameserver from one RaQ to another

["Rodolfo J. Paiz" <rpaiz@xxxxxxxxxxxxxx>]

At 7/4/01 01:01 PM +0100, you wrote:
> My current set up is this:
> RaQ3i as primary nameserver w/ virtual hosting
> RaQ4i (#1) as secondary nameserver w/ virtual hosting
>
> I have just purchased a new RaQ4i (#2), and I am migrating all the virtual
> sites from the old RaQ3i to this new machine.

1. Create all the sites on RaQ4i-#2 and put all the files in place. Make 
sure that the server is fully set up for virtual hosting and that it'll 
answer any queries you send it.

> My problem is this: How do I change things so that the new RaQ4 becomes our
> primary nameserver?

2. Moritz already told you how to do this. The procedure described will 
tell RaQ4i-#2 what answers to give for DNS (i.e. how to act as the primary 
nameserver). The edits he mentioned are so that www.domain1.com, 
www.domain2.com, www.domain3.com, and all the other DNS records that 
pointed to RaQ3i now point to their new home, RaQ4i-#2.

This is not an optional step!

3. Up to this point, you're setting up RaQ4i-#2 but all traffic is still 
going to RaQ3i. Now go to the registry and change the IP of the name server 
from RaQ3i to RaQ4i-#2. Now all the traffic will go to your new RaQ when 
the registry gets asked.

> Has anyone done this before?  How much disruption will it cause?

Yes, and anything between none and total disruption of business. Just 
depends on how well you do it.

Seriously, it shouldn't cause much disruption, as long as you:

a. setup the new RaQ first
b. then switch the registry info (whois)
c. then LEAVE THE OLD SERVER ON for another week or so

This will ensure that anyone with old, cached DNS records still gets an 
answer by going to the old server. When their cache expires, they'll go to 
your new server. In the traffic graphs, you'll see the traffic tapering off 
the first server. A week after the stuff is switched over, you can unplug 
the first one.

BTW, you could avoid this weekly delay by setting the TTL value in the SOA 
to something really short, like one minute. But if you're not sure what 
this means, then either go research it properly or don't try it at all, OK? 
Better to delay handing over the server for a week and do it the way you're 
comfortable.


--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx