Upgrading BIND with new hardware and new IP address

[Stefan Puiu]

Well what's the problem? You should be able to keep the old
configuration if you move to 9.3.1, and replace the old IP in your
zones with the new one, wherever it is used. Then you need to
configure your client machines to use the new DNS server and that's
it, unless you've left out something.

Also, since clients are configured with IP addresses of nameservers
(otherwise resolution would be deadlocked), you don't need to care
about names.

If you're not too knowledgeable about DNS or BIND, a book might help;
most people here suggest "DNS & BIND, 4th edition" by Cricket Liu and
Paul Albitz, and I agree it's quite good. It's slightly outdated with
regard to newer features in BIND since 9.1.0, but for that you have
the ARM ("Administrator's Reference Manual").

On 8/23/05, Church, Simon <schurch at lifemasters.com> wrote:
> Thanks - but what is the best way to upgrade the software and switch
> hardware at the same time? We also have to figure out the best way to
> change the IP address as well. I am trying to get a sense of how much
> can be done in one go or how we should be phasing this work.
>=20
> Simon
>=20
> -----Original Message-----
> From: Danny Mayer [mailto:mayer at gis.net]=3D20
> Sent: Tuesday, August 23, 2005 9:29 AM
> To: Church, Simon
> Cc: bind-users at isc.org
> Subject: Re: Upgrading BIND with new hardware and new IP address
>=20
> Church, Simon wrote:
> > Hello,
> > We have an existing server (e.g. EXTDNS01) running windows 2000 and=3D2=
0
> > BIND 9.21. We need to move this to new hardware, upgrade to the latest
>=20
> > version of BIND and also change the IP address of our server and=3D20
> > register it with the appropriate organization.
> >=3D20
>=20
> Upgrade. BIND 9.2.1 is so far beyond in used by date that you will not
> be able to sort out the difference between bugs and other problems.
> In this case that version has windows architectural problems and you
> shouldn't be using it.
>=20
> Danny
> > This server is also a slave to our master name server (e.g. EXTDNS01),
>=20
> > so we do have some fault tolerance if this server is down for a period
>=20
> > of time. I can also keep the old server online for as long as=3D20
> > necessary, so I could potentially set up the new server as a second=3D2=
0
> > slave server (e.g. EXTDNS03). If I did this, I would have to rename=3D2=
0
> > the server later on to EXTDNS02. Does BIND handle name changes OK?
> >=3D20
> > I am looking for recommendations on how best to get this new server on
>=20
> > line. How should I go about the upgrade to the latest version of BIND=
=3D20
> > as well as changing the hardware at the same time?
> >=3D20
> > Thanks,
> > Simon
> >=3D20
> >=3D20
> >=3D20
> > This electronic transmission, and any documents attached hereto,
> contains or may contain confidential, proprietary and/or privileged
> information. The information is solely for use by the intended
> recipient. If you are not the intended recipient, please immediately
> notify the sender and delete the electronic transmission (including any
> attached documents) and all copies thereof. Any unauthorized disclosure,
> copying, distribution, or use is strictly prohibited.
> >=3D20
> Then you shouldn't have sent this message to this list as it is not only
> public but also archived and searchable by search engines like Google.
>=20
> Danny
>=20
>=20
>=20
> This electronic transmission, and any documents attached hereto, contains=
=3D
>  or may contain confidential, proprietary and/or privileged information. =
=3D
> The information is solely for use by the intended recipient. If you are n=
=3D
> ot the intended recipient, please immediately notify the sender and delet=
=3D
> e the electronic transmission (including any attached documents) and all =
=3D
> copies thereof. Any unauthorized disclosure, copying, distribution, or us=
=3D
> e is strictly prohibited.
>=20
>=20
>