Question : How to configure DNS on Multiple DCs (AD integrated)

We have 15 DCs in total and we intend to make all DNS and GC.
6 are in a central location on a 100gig LAN connection.  We have made 6 seperate sites to divert client login to specific DCs.
6 are on remote sites with 4Mb connectivity to central site.  
2 are in data centers with 34Mb connections and serve at least 20 remote small sites.

I have configured my first win2k3 DC + DNS + GC (Currently this has all FSMO roles but this will chaneg as we add the other DCs).

I am about to install and add the other DCs next week.  

Q1) When I install the DNS service on the new DCs, How do I configure these? DO I configurte them as secondaries and let AD integration take care of replication?  Please put details in your answers including inatll and config stages.

Q2) As these DCs/DNS servers are AD integrated, DO I have to worry about DDNS records being replicated to ALL DCs?  I will have 5 dedicated win2k3 DHCP servers that serve 80 VLANs.  We use the router Helpers to divert the clients on specific vlans to the specific DHCP servers.    The DHCP servers will be configured with specific userid and password to update DDNS records on behalf of the clients.  My worry is that the 8500 clients will create a lot of DDNS replication traffic as part of AD integrated replication.  

I need this answer urgently.   Thanks

Answer : How to configure DNS on Multiple DCs (AD integrated)

Use Primary Active Diectory integrated zones.

By making them all Primary Active Directory zones you gain the following benefits:

They will all be able to make changes to the DNS database as needed.  
They will all be able to accept Dynamic Registrations.
No special configuration needs to be done to set up replication of the zone information.
No single point of failure (If you use Standard Primary and Secondary zones if you lose the Primary server you can't make updates until it is fixed).
You can set one of the DNS servers in each site upwith DHCP to handle Dynamic IP assignment and DNS registrations so there will be less traffic across the slower links (not a big issue in this case but good planning anyway)

Need more?  :-)

Dave Dietz