TABLE OF CONTENTS | 2.1 | Plan a host name resolution strategy. |
| 2.1.1 | Plan a DNS namespace design. |
| 2.1.2 | Plan zone replication requirements. |
| 2.1.3 | Plan a forwarding configuration. |
| 2.1.4 | Plan for DNS security. |
| 2.1.5 | Examine the interoperability for DNS with third-party DNS solutions. |
As a Windows 2000 MCSE, you understand how crucial a properly designed and configured host name resolution strategy is for your Windows network to run properly. In Windows Server 2003, the way you plan your host name resolution strategy is (in some ways) even more crucial than before. As we've seen in recent years, the Domain Name System (DNS) has become a victim to several attacks. Initially, DNS was designed as an open protocol, a fact that has now left it open to various threats, including footprinting, denial-of-service (DoS) attacks, data modification, and DNS redirection. Windows Server 2003 has made strides in preventing these types of attacks on your infrastructure through various security features, which we discuss at length within this chapter.
In addition to these new security features, Microsoft has added several other new features to DNS in the 2003 family, including:
Stub zones
DNS zone replication in Active Directory enhancements
Round-robin enhancements
Enhanced logging for debugging
EDNS0
Automatic name service record registration
Each of these new features will enhance your ability to provide a solid, functional DNS architecture for your environment. As with the new security features, we discuss each of these additional enhancements at length within this chapter to...
