Examining Your Current Environment


Before you deploy Windows Server 2003 DNS, you must assess your current environment to determine the DNS needs and constraints of your organization. After that, create a Windows Server 2003 DNS deployment plan to match those needs and constraints. Figure 3.2 shows the process for examining your current environment.

click to expand
Figure 3.2: Examining Your Current Environment

Determining Internet Status

If you want devices outside your private network to be able to resolve names belonging to your internal namespace, your IP addresses and DNS domain names must be registered with an Internet registration authority (Internet registrar). Internet registrars are organizations that are responsible for:

  • Assigning IP addresses.

  • Registering DNS domain names.

  • Keeping public records of registered IP addresses and domain names.

If your network is currently or will be connected to the Internet, you must ensure that the domain name of your organization is valid and registered to you.

Identifying the DNS Data Host

Determine who will host your DNS data. You can either host your DNS data on your own DNS servers or you can have an external ISP host your DNS data. By hosting your own DNS data, you have complete control of network resource allocation and security. Use an ISP if you have a small network that will not be expanding rapidly in the near future.

If you decide to use an ISP to host your DNS data, ensure that the DNS infrastructure of the ISP can support your DNS deployment.

Even if you decide to host your own DNS data, you might consider using an ISP to resolve names outside your private network. For example, the company contoso.com might decide to host all names belonging to the internal namespace corp.contoso.com on its own DNS servers while using an ISP to enable its employees to resolve external Web addresses such as www.microsoft.com.

Analyzing Your Network Topology

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.




Microsoft Corporation Microsoft Windows Server 2003 Deployment Kit(c) Deploying Network Services 2003
Microsoft Corporation Microsoft Windows Server 2003 Deployment Kit(c) Deploying Network Services 2003
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 146

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net