tailieunhanh - The Best Damn Windows Server 2003 Book Period- P71

The Best Damn Windows Server 2003 Book Period- P71:The latest incarnation of Microsoft’s server product,Windows Server 2003, brings many new features and improvements that make the network administrator’s job chapter will briefly summarize what’s new in 2003 and introduce you to the four members of the Windows Server 2003 family: the Web Edition, the Standard Edition, the Enterprise Edition, and the Datacenter Edition. | 666 Chapter 20 Planning Implementing and Maintaining a Name Resolution Strategy Designing a DNS Namespace Designing a DNS namespace is a critically important function for any business that relies on both the public and the private identities provided by the DNS namespace s for interaction with its customers and for the smooth and secure operation of its should take some of the following considerations into account Uniqueness Domain names on the Internet must be unique. Although it is not a requirement that your internal domain namespace be unique it is prudent to ensure its uniqueness. Integration and interaction of public and private DNS namespaces It is possible to use the same or different DNS namespace s for the public and private networks. Each of these alternatives provides different challenges. To separate the public and private zones requires both planning and administrative effort. Security Designing a DNS namespace should take into account the security requirements and configuration of your network. For example it is extremely inadvisable to allow any RRs that are specific to your internal network to be publicly available through DNS should set up separate name servers to respond to queries for the IP addresses of the organization s Internet hosts such as Web and mail servers. Deploying a private root zone can also help to enhance the security of your DNS infrastructure. Additionally you need to consider firewall placement and access rules when designing the DNS namespace. Administration The design of the DNS namespace will affect administration. For example using the same domain namespace for both the private and the public networks will require at a minimum a split DNS configuration where two name servers one that is authoritative for the public RRs and one that is authoritative for the private RRs will need to be implemented and maintained. In this scenario special configurations might need to be implemented to allow users on .