Domain Controller Dns Settings Best Practice 2012 R2
9 minutes to read.
Domain controller dns settings best practice 2012 r2. In a larger environment at least two domain controllers at each physical site. I ve seen lots of discussion on this topic. Domain controllers dcs will not replicate with each other on reguler interval.
What is the best practice for dns order on domain controllers. The value for preferred dns server remained the same the ip address of the windows server 2003 but as alternate dns server was set the loopback ip address of the newly promoted domain controller windows server 2012 r2 i e. 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.
This is also microsoft s recommendation. Dns configuration best practice on domain controllers clients and member servers. The new 2012 servers also have dns installed and i want to make sure all the dns config is correct.
This was kosher back in the day but modern windows networks do not like to see this. Domain controllers should not be multi homed 2. Never use the loopback address 127 0 0 1 as an entry in the dns settings.
Servers and workstations will go out of sync with regards to domain resources. Best dns order on domain controllers. Sandesh dubey july 16 2015.
Symptoms of miss configuration on nic on domain controller dc. This article describes best practices for the configuration of domain name system dns client settings. Windows server 2012 dns best practices.