Domain Controller Preferred Dns Server Best Practices
It is possible to install dns on servers which are not dcs including non windows servers but installing dns on dcs allows the use of ad integrated lookup zones see below which improve security and simplify zone replication.
Domain controller preferred dns server best practices. Symptoms of miss configuration on nic on domain controller dc. If the server is the first and only domain controller that you install in the domain and the server runs dns configure the dns client settings to point to that first server s ip address. Currently controller1 has 192 168 1 1 itself set as the preferred and nothing set for the alternate.
We ll see network latency. The dns server should have scavenging enabled which is a mechanism for performing cleanup and removal of stale resource records which can accumulate in zone data over time. What should the use the following dns server addresses fields be set to on the domain controllers themselves.
If you do a search on your own you will come across various answers but the majority recommends the configuration below. Best dns order on domain controllers. The results after running best practices analyzer have showed a warning dns.
Why shall we use best practices. I suppose the correct configuration is the following. Another dns secondary dns.
Controller2 has 192 168 1 1 set as the preferred and 127 0 0 1 as the alternate. Each dc dns server points to its private ip address as primary dns server and other internal remote dns servers as secondary dns in tcp ip property. Dns configuration on domain controller.
In a small environment at least one domain controller dc should be a dns server. Hello i would like an answer about the configuration of dns on the domain controllers. On a domain controller that also acts as a dns server microsoft recommends that you configure the domain controller s dns client settings according to these specifications.