Re: Server is Moving
- From: "ObiWan [MVP]" <obiwan@xxxxxxxx>
- Date: Tue, 23 May 2006 08:57:16 +0200
<snip>
Does anyone have any tips and possible steps to take<snip>
The best thing to do would asking your current DNS hoster to
setup a temporary DNS service for you, or arrange things to
place a "plug" machine there to serve as temporary DNS, at
that point you will relocate your server, update the zone file as
needed and then ask your hoster to switch the temp DNS from
master to slave and transfer the zone from your new DNS, this
will avoid "loosing your zone in outer space" due to propagation
and caching issues :-)
to sum it up
1) setup the replacement DNS as master for your zone using the
current zone data; just ensure to lower the TTL for the records
and for the SOA to make transition faster
2) relocate the DNS, setup the zone as needed (keep TTL low)
and update all the records as needed;
3) setup the relocated DNS as primary and switch the "old" DNS as
secondary, ensure that the secondary will immediately transfer a
copy of the zone, also ensure that the secondaries for the zone
will accept and use "notifies" to speed up things
4) wait some time (the low TTL will help) for zone propagation, then
remove the old DNS from the zone and shut it down or at least
remove your zone from it
5) set the TTL values back to regular and you should be ok
Regards
--
* ObiWan
Microsoft MVP: Windows Server - Networking
http://www.microsoft.com/communities/MVP/MVP.mspx
http://italy.mvps.org
.
- Follow-Ups:
- Re: Server is Moving
- From: vbnetdev
- Re: Server is Moving
- References:
- Server is Moving
- From: vbnetdev
- Server is Moving
- Prev by Date: Re: Problem with DNS
- Next by Date: Re: Question about DNS scavenging
- Previous by thread: Re: Server is Moving
- Next by thread: Re: Server is Moving
- Index(es):
Relevant Pages
|
