Windows Server R2 DNS Server Migration

Recently deployed vsphere Virtualization data Center for customers, after all deployment, migration operations completed, the customer put forward a new small requirements: the original production environment has a DNS server, the deployment of some applications, but the old disrepair is obsolete, but it has a DNS service, or to use, You want to migrate only the DNS service to the virtualization platform.

Because it's all Windows platforms, that's nothing. Well, look, our environment:

Original DNS server:

Host name: WIN08-01 IP Address: 10.200.201.11

The new DNS server (temporary hostname and IP address), because after the migration succeeds, the host name and IP address need to be changed to the same original DNS, the original DNS downtime.

Host name: WIN08-02 IP Address: 10.200.201.12

Are some of the test records we've prepared:

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/53/ae/wkiom1rthrctpshmaaiea2fp9uy153.jpg "height=" 362 "/>

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

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/53/ae/wkiom1rthrha6vdlaahimkxhx7k520.jpg "height=" 280 "/>

This figure shows the reverse lookup zone data.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/53/ae/wkiom1rthrlrcwiiaady8wz4yck842.jpg "height=" 279 "/>

Also includes a conditional forwarder.

The principle of DNS migration is actually simple:

The working mechanism of the DNS server is not complex, the DNS server relies 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 in the storage area. These files are in the \windows\system32\dns directory, of course, the specific information about these documents, we will not chat. As long as we get these files, we can fully implement the DNS migration.

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

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/53/ae/wkiom1rthrtafcq0aagq594eiam633.jpg "height=" 420 "/>

Because the DNS boot information can have three ways to save, 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 users mistakenly deleted the boot file, so by default the boot information is saved in two different ways.

Here, we can see the boot file directly by changing the startup of DNS to start from a file.

Step Two:

The next step is to install the DNS service on the server, and the process is no longer explicitly specified.

Step Three: Migration process

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

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/53/ae/wkiom1rthrsz262jaagwdzs3rzo971.jpg "height="/>

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

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/53/ae/wkiom1rthrazl9juaah8egu7jhw509.jpg "height="/>

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

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/53/ae/wkiom1rthrjcfoclaadvhuhx4xi056.jpg "height=" 260 "/>650) this.width=650;" Title= " Image "Style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0px;padding-top:0px; padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/ 53/ae/wkiom1rthrujh0v6aadgisiempq709.jpg "height=" 255 "/>

The Samples folder should not be copied because the content is not needed. When prompted, all are copied and replaced.

4 Restart the DNS service on the new server.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/53/ae/wkiom1rthr2ay22paah1usehhc8697.jpg "height=" 435 "/>

The new computer name and IP address are modified, just like the old server. The whole process is over and you can test it again. The entire migration process can be summarized as: Modify the service startup type on the old server, modify the service startup type on the new server, stop the service, copy the file, and start the service again. If you see it, congratulations, completed:

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/53/ac/wkiol1rthzjdp44waaimyco6_e4112.jpg "height=" 378 "/>

Here is the work of the testers, who can simply use the nslookup test and the others to swap the business unit. During testing, it is important to note that if the a record of other network segments is not resolved on the DNS server, it should be a problem with the DNS Server gateway test, and be careful to troubleshoot.

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

Windows Server R2 DNS Server Migration