Home > Articles

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

Chapter Summary

In the TCP/IP network of today's connected world, DNS is no longer a nicety; it's a requirement. Originally created to replace the antiquated and difficult-to-maintain HOSTS file, the domain name system (DNS) has quickly seen its popularity rise as TCP/IP has become the king of all networking protocols. Microsoft has lead the charge to make TCP/IP and DNS the de facto standards for all networks, small and large.

Because DNS is so critical to a Windows Server 2003 network, it is important that you prepare adequately before implementing your DNS solution. Only through proper prior planning can you be reasonably well assured of not having any problems down the road. The first decision you will need to make is what your DNS namespace will look like. You will need to choose from using an existing, delegated, or unique namespace.

After choosing your namespace, you can determine what types of zones you will require as well as how you will configure forwarding to occur. You will, of course, also want to look into securing your DNS infrastructure from attack and compromise. By choosing an Active Directory–integrated zone, you can ease administrative burden and increase DNS security.

If you have other DNS systems in use on your network, you will need to decide what their role is to be in your Windows Server 2003 network. Will you upgrade these servers to a newer version that is compatible with and supports the DNS requirements of Windows Server 2003? If not, you should consider migrating their DNS zones over to your Windows Server 2003 DNS servers and then retiring these legacy DNS servers or making them secondaries for improved redundancy.

Although Windows Server 2003 networks do not normally require WINS, WINS is still very much alive and available for use to ensure that legacy Windows clients can actively participate in newer networks that use the more robust DNS for name resolution. You should have a good understanding of the basics of WINS, including the LMHOSTS file, and how to maintain and monitor WINS. WINS servers do not perform zone transfers, as do standard DNS zones; they replicate—the same term used for Active Directory–integrated DNS zones. You must be able to configure and manage WINS replication if your network is distributed over more than one site or has more than one WINS server.

When something goes awry with a TCP/IP configuration, you need to be able to determine the cause and required corrective action. Windows Server 2003 (and Windows XP) provide a suite of tools that you can use to troubleshoot TCP/IP configuration. You will most commonly find yourself relying on the ipconfig, ping, nbtstat, tracert, pathping, and nslookup command-line tools.

Key Terms

Before taking the exam, make sure you are comfortable with the definitions and concepts for each of the following key terms. You can use Appendix A, "Glossary," for quick reference.

  • Active Directory

  • Active Directory–integrated zone

  • B-node

  • Conditional forwarding

  • Discretionary Access Control List (DACL)

  • Domain name service (DNS)

  • Dynamic Host Configuration Protocol (DHCP)

  • DNS client dynamic update

  • DNS forwarder

  • DNS resolver

  • DNS Security (DNSSEC)

  • DNS slave server

  • Dynamic updates from DHCP

  • Fully qualified domain name (FQDN)

  • H-node

  • Internet Control Message Protocol (ICMP)

  • ipconfig

  • Iterative query

  • LAN Manager HOSTS (LMHOSTS)

  • Leaf

  • M-node

  • NetBIOS

  • nbtstat

  • pathping

  • ping

  • P-node

  • Push replication

  • Pull replication

  • Push/pull replication

  • Recursive query

  • Replication partner

  • Secure dynamic update

  • Standard primary zone

  • Standard secondary zone

  • Stub zone

  • Top-level domain (TLD)

  • tracert

  • Transmission Control Protocol/Internet Protocol (TCP/IP)

  • Tree

  • Windows Internet Naming Service (WINS)

  • Zone

  • Zone transfer

  • + Share This
  • 🔖 Save To Your Account