From the root DNS name, you'll break down your DNS architecture into zones. You can do this any way you want, but the easiest way is to base your zones on your Windows NT domain. To easily configure Windows 2000 Server DNS name resolution, place a host in a DNS zone that corresponds to each Windows NT domain. When you enable Active Directory DNS integration, all DNS data will be replicated in Active Directory. When you design your DNS architecture this way, the DNS zone contains all the entries needed by the domain controller in the domain.
Any domain controller can act as a fully functional DNS server.
Not every domain controller needs to be a DNS server, but each site that has a domain controller should have at least one DNS server. After you've created your DNS domains, you can break them down further into subdomains. Because your subdomains are in the same DNS zone, you can use the same DNS server and one DNS database to cover all the subdomains. As we mentioned, when you design your DNS architecture, you should take the structure of your network and organization into account. The locations of your servers, users, and other network resources can impact how you design your DNS zones.