Windows Server 2008 R2 DNS Server Migration Method _win Server

Because it's all Windows platforms, it's nothing. Well, take a look at our environment:

Original DNS server:

Host name: WIN08-01 IP Address: 10.200.201.11

New DNS server (temporary hostname and IP address), because after successful migration, the host name and IP address will be changed to the same as the original DNS, the original DNS shutdown.

Host name: WIN08-02 IP Address: 10.200.201.12

The following figure is a few of the test records we've prepared:

This figure shows the forward lookup zone data, which includes a record, MX record, CNAME record, empty domain name resolution, and so on.

This figure shows a reverse lookup zone data.

In addition, a conditional forwarder is included.

The principle of DNS migration is simple:

The DNS server's working mechanism is not complicated, the DNS server relies entirely on several files in the background, one is the boot file, which is responsible for storing the startup information of the DNS server. One is Cache.dns, which is responsible for storing the domain name and IP address of the root server; One of the most important files is the zone data file, which is responsible for all DNS records within the storage area. These files are in the \windows\system32\dns directory, of course, on the specific information of these documents, we will not chat. As long as we get these files, we can fully implement the DNS migration.

Another point is that the boot file may not be visible to the background file directory where we open DNS because DNS is started by default from the registry. If it is started from the registry, we need to export the registry and then import it into the registry.

Because the boot information for DNS can be saved in three ways, one can be saved in the boot file, two can be saved in the registry, and three can be saved in active Directory. Microsoft may be afraid that the user mistakenly deleted the boot file, so by default, the bootstrap information is saved in two different ways.

Here, we can start the boot file directly from the start of the DNS, and then we can see the boot files.

Step Two:

Next, is to install the DNS service on the server, the specific process is no longer explicitly.

Step three: the migration process

1. Modify the service startup type of the DNS server to start with a file:

2. Stop the DNS service on the new DNS server as shown in the following illustration:

3. Copy the files from the DNS folder on the original DNS server to the new DNS server, as shown in the following illustration:

You should not copy the Samples folder because you do not need the contents of it. When prompted, all are copied and replaced.

4 Restart the DNS service on the new server.

The new computer name and IP address are modified, same as the old server. The whole process is over, test it again. The entire migration process can be summed up as: Modify the service startup type on the old server, modify the service startup type on the new server, stop the service, copy the files, and start the service again. If you see the image below, congratulations, complete:

The following is the work of the tester, you can simply use the nslookup test, the other is to exchange business units. During the testing process, it should be noted that the DNS Server gateway test should be a problem when testing a record of other segments on a DNS server that is not resolvable.

This article is from the "Duffy" blog, please be sure to keep this source http://dufei.blog.51cto.com/382644/1580057