Planning, Implementing, and Maintaining a Name Resolution Infrastructure
- Introduction to DNS
- Planning a DNS Namespace Design
- Planning DNS Zone Requirements
- Planning DNS Forwarding Requirements
- Configuring DNS Security
- Integrating with Third-Party DNS Solutions
- Introduction to WINS
- Implementing WINS Replication
- Implementing NetBIOS Name Resolution
- Troubleshooting Name Resolution Problems
- Chapter Summary
- Apply Your Knowledge
In today's well-connected network-centric world, name resolution is a critical component of any Windows Server 2003 network. The domain name system (DNS) is often considered one of the "critical" core network servicesand rightfully so. The Windows Internet Naming Service (WINS) has fallen out of favor with the move away from the Network Basic Input/Output System (NetBIOS) and NetBIOS Extended User Interface (NetBEUI), but it is still lingering in the background for many administrators who are faced with maintaining a heterogeneous network environment. Despite the fact that Windows Server 2003 (and Windows 2000 Server for that matter) runs on Transmission Control Protocol/Internet Protocol (TCP/IP) through and through, many networks still must support legacy Windows 9x and NT clients; thus, WINS still has a small place in Windows Server 2003 and therefore in this MCSE exam.
Microsoft has defined the name resolution portion of the "Planning, Implementing, and Maintaining a Network Infrastructure" objectives as follows:
Plan a host name resolution strategy.
- Plan a DNS namespace design.
- Plan zone replication requirements.
- Plan a forwarding configuration.
- Plan for DNS security.
- Examine the interoperability of DNS with third-party DNS solutions.
DNS is king when it comes to name resolution in Windows Server 2003 networks. Proper prior planning is essential to implementing a functional DNS environment for your network. Planning for DNS involves many different processes and steps, however, and you must be aware of them all to be able to create the correct DNS infrastructure you require.
Plan a NetBIOS name resolution strategy.
- Plan a WINS replication strategy.
- Plan NetBIOS name resolution by using the LMHOSTS file.
Even though Microsoft has officially moved away from WINS as the primary name resolution, it still exists to provide backward compatibility with legacy clients, such as Windows 98 and Windows NT 4.0 computers. You need to have a basic understanding of how WINS is configured to provide name resolution for your legacy clientsand do well on the exam.
Troubleshoot host name resolution.
- Diagnose and resolve issues related to DNS services.
- Diagnose and resolve issues related to client computer configuration.
DNS is one of those core network services that works right almost all the time. However, when the day comes that "DNS is broken," you will most certainly hear about it. In addition to the complaints your users will undoubtedly flood you with, your network may very well come to a screeching halt because Active Directory is extremely dependent on a functional DNS infrastructure. Being able to quickly identify and correct DNS-related problems is an essential part of your duties as the network administrator.
Introduction to DNS
- Fully Qualified Domain Names (FQDNs)
Planning a DNS Namespace Design
Planning DNS Zone Requirements
Planning DNS Forwarding Requirements
Configuring DNS Security
- Dynamic Updates
- Active Directory DNS Permissions
- Zone Transfer Security
- DNS Server Properties
- DNS Security (DNSSEC)
Integrating with Third-Party DNS Solutions
Introduction to WINS
- What's New in Windows Server 2003 WINS
Implementing WINS Replication
Implementing NetBIOS Name Resolution
Troubleshooting Name Resolution Problems
Apply Your Knowledge
- Review Questions
- Exam Questions
- Answers to Review Questions
- Answers to Exam Questions
Suggested Readings and Resources
Be sure that you have a thorough understanding of the WINS service and NetBIOS name resolution. Although this is a legacy Microsoft protocol, it is still required in many environments, and Microsoft wants to be absolutely sure you understand how it works.
Review the use of the monitoring tools and the different parameters of WINS that can be monitored. In its exams, Microsoft has focused a great deal of attention on the monitoring and troubleshooting of the different services, including the WINS service.
Get your hands dirty. The Step by Steps throughout this book provide plenty of directions and exercises, but you should go beyond these examples and create some of your own. If you can, experiment with each of the objectives to see how they work and why you would use each one.
Just 10 years ago, TCP/IP was not the king when it came to network communications protocols. Windows NT 3.51 relied on the venerable NetBIOS Extended User Interface (NetBEUI) protocol by default, and NetWare servers could be counted on to understand only IPX/SPX. With the recent widespread adoption of the Internet by the masses, TCP/IP slowly started to creep into private networks of all sizes and purposes. Administrators and network designers began to see the power and flexibility that TCP/IP offered them, and Microsoft and Novell took note of the shift. It wasn't long before all operating systems provided support for TCP/IP, but it still was not the networking protocol of choice. With the introduction of Windows 2000, Microsoft made TCP/IP and the domain name system (DNS) integral parts of Windows Active Directory networks.