Introduction and summary of DNS knowledge

The first time a few years ago contacted the Active Directory, it was the leadership that required the deployment of the Active Directory. Although there were several books on hand, there was no time to study them carefully. While looking at the help side of the running Dcpromo began to deploy the directory, I believe that many people and I was almost, confusedly began to become Active Directory administrator. For DNS, because the installation prompts for automatic deployment, I'm sure a lot of people will not do much in this area (including me, too). I paid a lot for this-because I do not know DNS, so I do not know how to solve the problem of DNS. I have the habit of saving interesting posts on the forum (obviously saving directly is not saved), I keep the number of posts on DNS issues, accounting for the third place (I am also surprised).

But there is no systematic summary of DNS on the forums (which is, after all, a big part of a book that can be written). I have drawn some operational conclusions and summaries through my own collection of posts and the reading of reference books, plus my own experience. Hope to be helpful to everyone, because I am not good at DNS (in the forum I also rarely to friends to solve DNS problems), so I think there must be I write the wrong place, I hope that the owner can help correct (i thick-skinned). My real goal is to learn from this article what misconceptions I have about DNS (I'm pretty selfish).

Talk less and the book is the same.

Friends with experience in DNS domain deployment can sense that the Active Directory's DNS, DHCP, and wins (not much used) are closely related to NetBIOS. It's also easy to confuse. So it's a lot of trouble, usually when we start to deploy ad in a small company, there are about dozens of computers in the local area network. The flow of people is not very frequent, so the computer is also almost every day open. Very few computers change places, and we all use the default configuration of DNS to have very few problems. But we can not stay in such a place for a lifetime, we come to a relatively complex network environment, aware of their lack of DNS at least common sense, how to do? In order to be able to correctly express their own problems in the face of difficulties (otherwise people want to help you have no way, in addition to the up we are more important to speak clearly their own problems and understand the meaning of the master) so as I start from the foundation.

What kind of DNS system is a more perfect system? The continuity of the DNS server provides excellent performance, reducing traffic across the WAN, and security must be ensured.

Let's start with the concept.

1. DNS and Active Directory relationships

DNS defines "namespace" (namespace)----Microsoft has called "contoso.com" the name space, the host in this space is stored in a "zone file" (Zonefile)-mainly a mapping of the relationship (middle School mathematics has a mapping concept)

Domains in the Active Directory (domain) "stores objects in domains and domains", the user, and the SAM in the registry of the computer account group. --more than that, of course.

DNS and domain binding-Fully qualified domain name (FQDN): For example, srv1.contoso.com--explains that the SRV1 host is located in contoso.com domain.