From owner-freebsd-isp  Mon Jan 24 12:41:25 2000
Delivered-To: freebsd-isp@freebsd.org
Received: from benge.graphics.cornell.edu (benge.graphics.cornell.edu [128.84.247.43])
	by hub.freebsd.org (Postfix) with ESMTP id 99A4315AB0
	for <freebsd-isp@FreeBSD.ORG>; Mon, 24 Jan 2000 12:41:14 -0800 (PST)
	(envelope-from mkc@benge.graphics.cornell.edu)
Received: from benge.graphics.cornell.edu (mkc@localhost)
	by benge.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id PAA43470;
	Mon, 24 Jan 2000 15:41:11 -0500 (EST)
	(envelope-from mkc@benge.graphics.cornell.edu)
Message-Id: <200001242041.PAA43470@benge.graphics.cornell.edu>
To: Sean Michael Whipkey <highway@cstone.net>
Cc: freebsd-isp@FreeBSD.ORG
Subject: Re: Network renumbering (Yack!) 
In-Reply-To: Message from Sean Michael Whipkey <highway@cstone.net> 
   of "Mon, 24 Jan 2000 15:30:01 EST." <388CB649.820E6B7D@cstone.net> 
Date: Mon, 24 Jan 2000 15:41:11 -0500
From: Mitch Collinsworth <mkc@Graphics.Cornell.EDU>
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>daniel B wrote:
>> I dreaded this moment would come but I am in a position that I need to
>> change upstream and all DNS info is going to change, customer workstations
>> may have to be reconfigured ...
>> Since I haven't done this before what is the least painful way to handle
>> this task? is there a documented procedure/how-to somewhere?
>> Realy don't want to start guessing.
>
>We're in the middle of that right now, and all I can really think of to
>say is..."Sorry."  :-(
>
>It's rough.  We started by giving our servers multiple IP addresses, one
>old and one new.  We then moved our customers over slowly - first all of
>the static IP addresses, and then each phone number depending on how it
>was tied to a router.  We hired an outside consultant to do some of our
>network customers, which was a mistake.
>
>You just have to be patient...:)

I nominate this line for understatement of the month!  :-)

Another thing to consider it taking this as an opportunity to start
using DHCP for all non-server systems.  You might even want to use
it on some of your servers, though I haven't felt that brave yet.
This seems like a good idea even if you're not using dynamic addresses
since it puts all the network configuration info in one place where
it's easy to change when you need to.

-Mitch


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message