Re: [cobalt-users] moving to another noc

["E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>]

w> Date: Thu, 27 Feb 2003 11:56:08 +0100
w> From: wanadoo


w> i have plans to move my servers to another noc.

s/noc/data center/


w> This is my question:
w>
w> It is the first, and hopely the last move im making.
w> All the ipnumbers most be changed.

Correct.


w> I use 2 raq 4 for dns
w> how can i move whit as little down-time as possible.
w> Is it an idee to move the servers, change the ip's
w> move the first dns server, changa all te ip's, but
w> leave the secend dns server in place, but change the dns ip's
w> from the sites in this.
w> So the first dns works on the new ip's and the seccond catches
w> on the old ipnummber.

Yes.  Remember that, on the first server, you'll need to tell it
the new master for all the zones.


w> then after 7 days move the second dns server.

You should decrease the TTLs for your zones beforehand so you're
not waiting on stale cached information.  I do this by editting

	/etc/named/records

appropriately then using the GUI's "save changes" function.


w> Or am i thinking wrong.

You're on the right track.  You just need to decrease how long
DNS info is cached.


w> Anybody who has don this already ??

Yup.  Get everything lined up beforehand, and the transition can
be smooth and painless. :-)

IMPORTANT:  Be sure you contact your registrar and notify them of
the nameserver renumbering.  Otherwise you'll have stale glue
records, and ugly things will happen. :-(


Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.