Proper DNS Settings for 2 domain controllers

Hey guys - I am running two domain controllers (just added the 2nd one recently).  The 'first' domain controller is 2003 and uses itself for DNS of course, and has forwarders set up for the iSP's DNS.  All clients currently use this machine for DNS.  The 2nd domain controller (2008 R2) uses itself for DNS.  What other DNS settings do I need to change?  Should I point the clients to the 1st or 2 domain controller for DNS?    Thanks in advance for any help!
zagnutttt4Asked:
Who is Participating?
 
Mike KlineConnect With a Mentor Commented:
Clients can be pointed to either one.    What you have is fine but to avoid race condition issues you can point DC1 to DC2 for primary DNS and vice versa.  MOre on that here:

http://www.experts-exchange.com/Software/Server_Software/File_Servers/Active_Directory/Q_27556645.html

Having said that if you are not having any issues leaving it as is works too

Thanks

Mike
0
 
ZenVenkyArchitectCommented:
Both DCs shall point to themselves as preferred DNS and secondary as other DC's DNS. For better understanding check this link.

DNS Best Practices
0
 
Mike KlineCommented:
Zen,   I used to do it that way too until we ran into race condition issues a few years back at another job.

askds also talked about it here   http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx#dnsbest

Thanks

Mike
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
zagnutttt4Author Commented:
Will group policy changes made on either domain controller replicate to the other?
0
 
DrDave242Connect With a Mentor Commented:
Should I point the clients to the 1st or 2 domain controller for DNS?
You should point them to both, but which one should be the preferred server and which one should be the alternate is up to you.

Also, I'm in agreement with mkline71: Set each DC to use the other one as its preferred server and itself as alternate. Microsoft's DNS BPA agrees with this as well.
0
 
Nick RhodeIT DirectorCommented:
DNS Servers would point to each other for primary and then themselves as a secondary.  This prevents what is known as the "island effect".  Where the DNS servers isolate themselves.  

As for setting up DHCP and pushing DNS to the clients workstations you will choose which DNS server is your primary and which one is the secondary.
0
 
DrDave242Commented:
Will group policy changes made on either domain controller replicate to the other?
As long as your SYSVOL folder is replicating correctly between the two, Group Policy changes will replicate. Keep in mind that SYSVOL replication and AD replication are separate, and it is possible for one to fail while the other continues working perfectly.
0
 
ZenVenkyArchitectCommented:
MKline, I agree with you there is a an argument going on every blog which deals with AD and DNS. Because of that reason Microsoft didn't come to a conclusion to release DNS default configuration settings for DC I believe you agree with me. I've been using these DNS configurations from many years and never had any issues.

Point #2 what AskDS mentioned is for multi domain/ forest scenario but definitely not in small and medium business environments where you see not more than 15 DCs and it is surely single domain environment.

I'm not trying to say what I mentioned is the thumb rule for DNS configuration, it is just a best practice that I've been following and I never had any issues in small and medium business environments.
0
 
zagnutttt4Author Commented:
Thanks guys, I will try both ways, giving each method enough time to determine if any problems and/or performance issues are occurring.
0
All Courses

From novice to tech pro — start learning today.