DNS Config for Second AD Domain Controller

[pthompson2]

I have an existing Win2K/AD domain with a single DC. I would like to bring a second DC online for redundancy purposes. I am going to install DNS locally and make it a Global Catalog server in order to handle logon requests in the event of failure of the first DC.

My question is, what are the proper TCP/IP settings for the second DC? The original DC points to itself for DNS resolution. Should the new DC also point to itself for DNS resolution, or should it point to the the original first DC?

(Granted, I realize that in order to promote the new DC to a Domain Controller, it needs to point DNS to the original DC initially. I'm just wondering if after promotion it needs to point to itself.)

I'm concerned about inadvertently creating some sort of AD synchronization loop.

I'm having a heck of a time trying to get clarification on this. Any suggestions would be greatly appreciated!

 

[markdlane]

Active Directory requires DNS, but it does not require it on evey domain controller. You have a couple of options. Set up your DC2 and point it to DC1 for DNS. But if you really want redundancy, why not set up DC2 as a backup(secondary zone) for DNS or make both DNS servers Active Directory integrated? Then point DC2 to itself. Your "redundancy" is pointless without DNS running somewhere.