Caveats for moving bind from one server to another?
sam.pointer at hpdsoftware.com
Fri Jun 7 14:36:44 UTC 2002
-----BEGIN PGP SIGNED MESSAGE-----
What I have done in the past is to make the new nameserver a slave of
the old server and let the zone transfer automagically. This way you
can ensure that the new one is stable whilst keeping the old one
going. When everything seems OK then perform whatever the swap
entails (turning off the old box, swapping IP addresses, et al) and
make the minor config changes to turn your "new-old slave" into a
- -----Original Message-----
From: Christopher Crowley [mailto:ccrowley at tulane.edu]
Sent: 07 June 2002 15:38
To: bind-users at isc.org
Subject: Caveats for moving bind from one server to another?
*** PGP Signature Status: good
*** Signer: Christopher Crowley <ccrowley at tulane.edu> (Invalid)
*** Signed: 07/06/2002 15:38:02
*** Verified: 07/06/2002 15:51:48
*** BEGIN PGP VERIFIED MESSAGE ***
Just wanted to get feedback from you all about this.
We are replacing an older name server with a new box. We are
planning to: stop bind, tar up all the zone files, move them to the
new server, then start bind there. We will assign IP addresses
appropriately, and move the bind config files.
Most of the zones are static, but a few are dynamic.
Has anyone done this recently with 9.2.1? Any snafus that you
Thanks in advance for the response.
TIS Network Services
ccrowley at tulane.edu
PGP Key ID: 0x7CF18FDB
*** END PGP VERIFIED MESSAGE ***
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
-----END PGP SIGNATURE-----
This email and any attachments are strictly confidential and are intended
solely for the addressee. If you are not the intended recipient you must
not disclose, forward, copy or take any action in reliance on this message
or its attachments. If you have received this email in error please notify
the sender as soon as possible and delete it from your computer systems.
Any views or opinions presented are solely those of the author and do not
necessarily reflect those of HPD Software Limited or its affiliates.
At present the integrity of email across the internet cannot be guaranteed
and messages sent via this medium are potentially at risk. All liability
is excluded to the extent permitted by law for any claims arising as a re-
sult of the use of this medium to transmit information by or to
HPD Software Limited or its affiliates.
More information about the bind-users