Domain Controller Dns Settings Best Practice 2012
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 dns settings best practice 2012. Best dns order on domain controllers. Since it was the only one dns server in the domain it was using its loopback ip address as preferred dns server. If you do a search on your own you will come across various answers but the majority recommends the configuration below.
The recommendations in this article are for the installation of windows 2000 server or windows server 2003 environments where there is no previously. There were no issues for resolving names within the domain. Windows server 2012 dns best practices.
This was kosher back in the day but modern windows networks do not like to see this. Here is a photo of how a simple network card configuration should look on a windows server 2012 box that does double duty as a domain controller and a dns server. Best practices for dns client settings in windows 2000 server and in windows server 2003.
Dns settings of a single domain controller in active directory site. In a larger environment at least two domain controllers at each physical site. Never use the loopback address 127 0 0 1 as an entry in the dns settings.
The new 2012 servers also have dns installed and i want to make sure all the dns config is correct. 9 minutes to read. Finally whichever scheme you use for configuring dns server settings on domain controllers in your active directory environment you may want to also conduct a test to see what happens if all of the domain controllers in a site are suddenly shut down either gracefully or by an abrupt power failure.
This is also microsoft s recommendation. In my case here is what i had for dns on my windows server 2003 dc before introducing windows server 2012 r2. 19 thoughts on best practices for dns settings on dc and domain members.