Establishing an Active Directory integrated zones must be hosted by Domain Controllers and all Active Directory integrated zones are primary zones. Since we are speaking about where to put Domain Controllers is non every bit simple or cut clear but I believe any subdivision location that’s traveling to utilize this service benefits from holding a local DC and domain-integrated DNS services. There are some factors in where to put ; Domain members rely to a great extent on DNS services to turn up domain resources. over a slow nexus. the regular activities of authenticating against distant DCs. questioning domain resources. and executing other standard DNS searchs can make a sulky and slightly bad user experience and eventually. if the nexus between sites goes down and there is no local DNS service. your users won’t be able to shop the Internet unless you’ve configured secondary DNS waiters.
For a little subdivision office with 5 users and a slow nexus. you might be able to acquire off without a local DC/DNS waiter every bit long as users aren’t dependant on the ability to authenticate against the sphere. Non-domain DNS waiters are available to service questions in the event your site nexus goes down. Some DNS-enabled routers can selectively send on petitions for choice spheres to specific DNS waiters. This method eliminates the hold of neglecting over from a primary to secondary DNS waiters per client. Possibly A READ ONLY DOMAIN CONTROLLER For your larger subdivision office. I would decidedly urge proviso the site a local DC/DNS waiter.