When should I create a new Primary DNS Zone?
When should I create a new Forward Lookup Zone (primary zone) in my Active Directory DNS?
Since the option exists, I'm sure there are cases where it must be useful. And yet, it seems like most domains work just fine with the default single-zone configuration.
I've run into a few scenarios where it seems like a separate DNS zone could be useful, but I've never actually done so. So even if it's not required, could it be sometimes recommended?
- Multiple physical sites and a single domain. For a network that spans multiple physical offices, a DNS zone could be set up for each office. It should be easy to set up with Group Policy, but this might cause problems resolving DNS for roaming users.
- Wireless LAN. Having a separate DNS zone for wired/wireless interfaces would enable you to choose whether you connect to the wired or wireless interface on a client (remote admin).
- Split-horizon DNS. If there are internal servers that need to be accessed from both inside and outside the office network, then split-horizon DNS would allow the names to resolve to either internal/external IP addresses depending on where the client is connecting from.
For these scenarios (and others?) I am looking for the pros/cons of adding a new primary zone, and I'm also interested to know whether anybody has encountered this in a production network.