Server Replacement

[Michael E. Hanson]

Actually, if your name server is registered at Network Solutions and you
change its "HOST" entry there, the change will automatically filter into all
the Domains that are registered with NetSol that reference that name server.
_______________
Michael E. Hanson
President, Gryphon Consulting  Services
(http://www.GryphonsGate.com)
P.O. Box 1151
Bellevue, NE  68005-1151
(402) 871-9622

MEHanson at GryphonsGate.com (primary)
Gryphons_Master at yahoo.com
----- Original Message -----
From: "David Botham" <dns at botham.net>
To: <comp-protocols-dns-bind at isc.org>
Sent: Thursday, October 03, 2002 9:39 AM
Subject: RE: Server Replacement


>
>
>
> > -----Original Message-----
> > From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> > Behalf Of Clancy, Steve
> > Sent: Thursday, October 03, 2002 9:26 AM
> > To: comp-protocols-dns-bind at isc.org
> > Subject: Server Replacement
> >
> >
> > Greetings;
> > I'm getting ready to replace my current DNS server with a new machine.
> The
> > IP address will be different so I know I will need to change that with
> the
> > registrar. Any other gotchas I should be aware of?
>
> Yes.  I am fairly certain that even if you change the IP of the name
> server with your Registrar, that change will not filter into the
> delegation RR for the zones on that name server.
>
> In other words:  Let's say your name server is ns1.foo.com with IP
> 192.168.1.10 (that will be changed to 10.10.1.10).  Also, let's say that
> you have a domain that is registered to use that name server called
> bar.com.
>
> I am pretty sure you will need to make two changes here:
>
> 1.  Change your name server host record at the registrar for ns1.foo.com
> to reflect ns1's change in IP address to 10.10.1.10.
> 2.  Change the bar.com registration information to reflect the change in
> ns1's IP address to 10.10.1.10.
>
> I am sure you can see where the lag associated with these changes can
> cause a lapse in resolution if you are not careful.  This problem gets
> worse with an increase in the number of zones hosted on the name server.
> I recommend a process something like this:
>
> 1.  Create (and register) a new name server (say ns2) and load all the
> zones from the old name server on it.
> 2.  Make the old name server a slave to the new server (make changes on
> the new server, they will replicate to the old server).
> 3.  Make all the necessary changes with your registrar for all your
> domains.
> 4.  When you are sure that no one is using the old name server anymore
> (all delegation information is updated at the registrar and TTLs [gtld
> ttls are currently 2d] have expired), take the ole name server off the
> net.
>
>
> Dave...
>
> >
> > Thanks
>
>
>