• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 213
  • Last Modified:

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...
0
aheckman
Asked:
aheckman
  • 2
  • 2
2 Solutions
 
Jian An LimCommented:
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
0
 
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).
0
 
Jian An LimCommented:
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.

0
 
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!
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now