Today, the company set up AD domain, add on WinServer2012 AD domain functions, the IP address for 1192.168.0.4, domain name: vsphere.com (the original poster self-study virtualization), after completing the AD, open the DNS management tool, found two domain forward lookup zone, respectively is: the _msdcs. Vsphere.com and vsphere.com, backward region is empty, so creating corresponding reverse zones, the 192.168.0.0/24 mapped to the vsphere.com domain, the forward lookup zone below:


Reverse lookup zones are as follows:


Will join the domain, 192.168.0.1 in using nslookup commands, CMD prompt normal:


From the local DNS server (192.168.0.4) using CMD nslookup command:

According to the DNS server information is not correct,

Why, then, lead to the DNS native resolution is not correct, other machines to parse the normal?
In addition, if a new host (192.168.0.2) to join the domain, the DNS server can be normal, need not add corresponding PTR record?

CodePudding user response:

DC this server DNS should be configured to point to yourself

CodePudding user response:

Remember the book write nslookup unknown is because there is no PTR record, I think the building Lord screenshots show the address should be 127.0.0.1 address, and no PTR records of the record, should be related to this,

CodePudding user response:

DC DNS to their other refers to as DC machine

CodePudding user response:

192.168.0.4 DNS to oneself: 127.0.0.1; 192.168.0.2 192.168.0.4 DNS orientation,