Deploy first domain: Active directory Series bis

In the last blog post we introduced the meaning of the deployment domain, and today we are going to deploy the first domain. In general, there are three kinds of computers in the domain, one is the domain controller, the domain controller stores active Directory; One is the member server, which is responsible for providing services such as mail, database, DHCP and so on. There is also a workstation, which is the client used by the user. We are ready to build a basic domain environment, topology as shown in the following figure, Florence is a domain controller, Berlin is a member server, Perth is a workstation.

Deploying a domain generally takes the following tasks:

1 DNS Pre-preparation

2 Creating a domain controller

3 Creating a computer account

4 Creating a user account

A DNS pre-preparation

DNS servers are essential for domains, on the one hand, computers in the domain use DNS domain names, DNS needs to provide domain name resolution services for computers in the domain, and another important reason is that computers in the domain need to use the SRV records provided by DNS to locate domain controllers. So we need to do a good job of DNS preparation before we create a domain. So which computer is responsible for the DNS server? The general engineer has two choices, either using a domain controller to do the DNS server or using a separate DNS server. I usually use a stand-alone computer to act as a DNS server, this DNS server not only provides resolution services for the domain, but also provides DNS resolution support for other businesses of the company, and you can choose a DNS server based on the specific network environment.

What preparations do the DNS servers need to do before creating a domain?