Analyzing Your Network Topology

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Analyze your existing network topology and plan your DNS namespace while accounting for the service and administrative goals of your organization.

Allow for anticipated expansion of the number of nodes in your DNS hierarchy by including domain name placeholders between the domain names that you are initially deploying. Adding domain name placeholders enables you to avoid having to redesign your DNS infrastructure to accommodate additional domain names.

Anticipate the possibility of changes to your business model by assigning domain names that can be used in a modified context. For example, instead of using the domain name accounting.contoso.com, you might use finance.contoso.com, in anticipation of the possibility of expanding into additional financial services beyond accounting.

Diagram Your Existing DNS Infrastructure

If you are upgrading to Windows Server 2003, rolling out a new DNS deployment, or integrating Windows Server 2003 DNS with Active Directory, you might not need to make any changes to your existing DNS infrastructure. However, if you are migrating from a third-party DNS infrastructure or integrating Windows Server 2003 DNS with an existing third-party DNS infrastructure, create a diagram of your existing DNS infrastructure, including domains, servers, and clients. Use this diagram to assist you in deciding whether to make changes to your current DNS infrastructure when you deploy Windows Server 2003 DNS.

Identify Your Security Policies

Identify and document your organization’s security policies before you begin to design and deploy your DNS infrastructure. In this way, you can ensure that your DNS servers, zones, and resource records support these policies. For more information about security policies, see "Deploying Security Policy" in Designing a Managed Environment of this kit.