TABLE OF CONTENTS | 3.1 | Design a DNS name resolution strategy. |
| 3.4 | Design a DNS service implementation. |
| 3.1.1 | Create the namespace design. |
| 3.1.5 | Design a DNS naming strategy for interoperability with UNIX Berkeley Internet Name Domain (BIND) to support Active Directory |
| 3.4.3 | Identify the registration requirements of specific DNS records. |
| 3.1.3 | Specify zone requirements. |
| 3.1.4 | Specify DNS security. |
| 3.4.1 | Design a strategy for DNS zone storage. |
| 3.1.2 | Identify DNS interoperability with Active Directory, WINS, and DHCP. |
| 3.4.2 | Specify the use of DNS server options |
| 3.2 | Design a NetBIOS name resolution strategy. |
| 3.2.1 | Design a WINS replication strategy. |
The next chapter deals with name resolution strategies. Specifically, we discuss DNS and WINS considerations in this chapter, and how best to implement these technologies so as to provide an efficient, robust, scalable, and available name resolution strategy.
Unlike prior versions of Windows, which relied heavily on WINS as their primary resolution mechanism, Windows 2000 and Windows Server 2003 primarily use DNS for name resolution. The first subjects discussed are the implementation of DNS, the namespace, and how Active Directory may be dovetailed into any existing Berkeley Internet Name Daemon (BIND) deployment.
Next, we discuss zones and their configuration and storage options, followed by the strategies for securing the namespace, servers, zones, and records through delegation. We then examine how DNS records need to be registered by various types for name resolution to function properly. A description of how to make full use of the interoperability of DNS, WINS, and DHCP...
