2 Primary Servers vs 1 primary 1 Secondary

Looking at the 'Properties' on one of my Forward Look-up zones, on the 'General' tab there is a setting to change the 'Zone Type'. When clicking on this, I can choose between Primary Zone, Secondary Zone, or Stub Zone with a brief description of each. My primary DNS/DC server is set as 'Primary Zone,' I have a secondary DNS/DC server also set as 'Primary Zone,' This is all on a single Domain environment with approx. 300 PCs . Should my secondary DNS/DC server be set as 'Secondary Zone' or remain as 'Primary Zone' and what are the implications? I want to have a completely fault tolerant set-up...
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jian An LimSolutions ArchitectCommented:
Usually for Domain controller, you will set as Active Directory-intergrated and it will be primary.

the benefit of doing this is all your DNS information is replicated as part of your Active Directory

I won't think about secondary zone and etc. those applicable if you got something more complicated then 2 servers

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aheckmanAuthor Commented:
Take this one step further for me...  we have 4 sites (hub and spoke).  Hub site has the 2 DNS/DC's.  Each spoke has a DC.  Do you think it would be appropriate to change those spoke DC's into DNS servers to lessen the amount of DNS traffic over WAN links.  (Not that i think that traffic is cluttering the lines, but in an overall design aspect).
Jian An LimSolutions ArchitectCommented:
one thing you need to take account into is all DC replicated to each other all time. (or spoke to hub). Putting the DNS record into AD replication will not burden the replication (unless we are talking 128KB) here. Further, IT only replicate once .. then keep replicating for the reset of your time. And if you update DNS  on your spoke server, you will get updated in hub.

If you have only secondary server, everytime u need to change your dns settings, you need to send the request through the link to the hub DNS and it then replicated back to spoke DNS..

even you put in sencondary dns, it still need to do a zone transfer from the HUB server, it is either make the changes now or later compare to secondary dns..

Unless you got a great concern about the security in your spoke server, i wont think much of putting a secondary out there.

aheckmanAuthor Commented:
There's really no finite solution here.  I looked for more opinions than answers, however only one person responded.  I'm grateful for their response so i gave them the points.  Thanks you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.