The root domain name of the Windows domain controller is exactly what is set, the average person may not think at all, but for OCD patients this must be understood to do.
This is a tangle of my long-time problem, there are two tangled points:
First, do you need to set up a real domain name?
Second, is DNS pointing to the school's DNS, or is it a DNS service built with Windows?
650) this.width=650; "Src=" https://s3.51cto.com/wyfs02/M02/98/2A/wKiom1k4DbzSOLXAAAClVVlc9gk257.png-wh_500x0-wm_ 3-wmp_4-s_2517175535.png "title=" Qq20170607222321.png "alt=" Wkiom1k4dbzsolxaaaclvvlc9gk257.png-wh_50 "/>
I thought about it a little bit today and suddenly became enlightened.
According to Microsoft, the number of PCs in a company's network is less than 10 recommended in workgroup mode, with more than 10 recommended domain-based management models.
First, this network may be a dedicated network, private network, there is no DNS resolution server, so this domain name does not need to be real.
Second, DNS is placed on the school's DNS resolution server is not available, provided that DNS has a hot standby or cluster. I personally think that the domain controller is built on the DNS service is more secure, anyway, bad some bad. In addition domain controller we do at least two units, one bad. does not affect the normal use of domain users.
This article is from the "University Network and data center operation and Maintenance" blog, please make sure to keep this source http://hanson2017.blog.51cto.com/1336475/1933261
Windows domain controller root domain settings