DNS on Windows 2000 is a special Windows-oriented edition of the classic DNS and BIND. The Domain Name System (DNS) is one of the Internet's fundamental building blocks: the distributed host information database that's responsible for translating names into addresses, routing mail to its proper destination, and many other services. As the preface says, if you're using the Internet, you're already using DNS--even if you don't know it.
Besides covering general issues like installing, setting up, and maintaining the server, DNS on Windows 2000 tackles those specific to the Windows environment: integration between DNS and Active Directory, conversion from BIND to the Microsoft DNS server, and registry settings. You'll also acquire a grounding in:
Zone change notification
Planning for growth
If you're a Windows administrator, DNS on Windows 2000 is the operations manual you need for working with DNS every day; if you're a Windows user who simply wants to take the mystery out of the Internet, this book is a readable introduction to the Internet's architecture and inner workings.
What DNS does, how it works, and when you need to use it
How to find your own place in the Internet's namespace
Setting up name servers
Integrating Active Directory with DNS
Dynamic updates, storing zone information in Active Directory, and incremental zone transfers
Using MX records to route mail
Configuring hosts to use name servers
Subdividing domains (parenting)
Securing your name server: preventing unauthorized zone transfers
Mapping one name to several servers for load sharing
Troubleshooting: using nslookup, diagnosing common problems
Chapter 1 Background
A (Very) Brief History of the Internet
On the Internet and Internets
The Domain Name System, in a Nutshell
The History of the Microsoft DNS Server
Must I Use DNS?
Chapter 2 How Does DNS Work?
The Domain Namespace
The Internet Domain Namespace
Name Servers and Zones
Chapter 3 Where Do I Start?
Which Name Server?
Choosing a Domain Name
Chapter 4 Setting Up the Microsoft DNS Server
The DNS Console
Setting Up DNS Data
Running a Primary Master Name Server
Running a Slave Name Server
Adding More Zones
Chapter 5 DNS and Electronic Mail
Adding MX Records with the DNS Console
What’s a Mail Exchanger, Again?
The MX Algorithm
DNS and Exchange
Chapter 6 Configuring Hosts
Advanced Resolver Features
Other Windows Resolvers
Sample Resolver Configurations
Chapter 7 Maintaining the Microsoft DNS Server
What About Signals?
Updating Zone Data
Zone Data File Controls
Chapter 8 Growing Your Domain
How Many Name Servers?
Adding More Name Servers
Registering Name Servers
Planning for Disasters
Coping with Disaster
Chapter 9 Parenting
When to Become a Parent
How Many Children?
What to Name Your Children
How to Become a Parent: Creating Subdomains
Subdomains of in-addr.arpa Domains
Managing the Transition to Subdomains
The Life of a Parent
Chapter 10 Advanced Features and Security
DNS NOTIFY (Zone Change Notification)
Name Server Address Sorting
Building Up a Large Sitewide Cache with Forwarders
A More Restricted Name Server
A Nonrecursive Name Server
Securing Your Name Server
Chapter 11 New DNS Features in Windows 2000
Aging and Scavenging
Incremental Zone Transfer
Unicode Character Support
Chapter 12 nslookup
Is nslookup a Good Tool?
Interactive Versus Noninteractive
Avoiding the Search List
Troubleshooting nslookup Problems
Best of the Net
Chapter 13 Troubleshooting DNS
Is DNS Really Your Problem?
Checking the Cache
Potential Problem List
Chapter 14 Miscellaneous
Using CNAME Records
A Limitation of MX Records
DNS and Internet Firewalls
Network Names and Numbers
Additional Resource Records
Appendix DNS Message Format and Resource Records
Master File Format
Resource Record Data
Appendix Installing the DNS Server from CD-ROM
Appendix Converting from BIND to the Microsoft DNS Server
Step 1: Change the DNS Server Startup Method to File
Step 2: Stop the Microsoft DNS Server
Step 3: Change the Zone Data File Naming Convention
Step 4: Copy the Files
Step 5: Get a New Root Name Server Cache File
Step 6: Restart the DNS Server
Step 7: Change the DNS Server Startup Method to Registry
Matt Larson started Acme Byte & Wire, a company specializing in DNS consulting and training, with Cricket Liu in January 1997. Previously, he worked for Hewlett-Packard, first as Cricket's successor as hp.com hostmaster, then as a consultant in HP's Professional Services Organization. Matt graduated from Northwestern University in 1992 with two degrees: a bachelor of arts in computer science and a bachelor of music in church music/organ performance. He lives in Bethesda, Maryland, with his wife, Sonja Kahler, and their two pugs. In his spare time he enjoys playing the 10-rank pipe organ in his house and flying light airplanes. Cricket worked for five and a half years at Hewlett-Packard's Corporate Network Services, where he ran hp.com, one of the largest corporate domains in the world, and helped design the HP Internet's security architecture. Cricket left HP in 1997 to start his own company, Acme Byte & Wire, with his friend and co-author Matt Larson. Network Solutions acquired Acme Byte & Wire in June of 2000, and then subsequently, Network Solutions merged with VeriSign. Cricket became Director of DNS Product Management of the merged company, helping determine which new DNS-related products VeriSign would offer.
Cricket Liu matriculated at the University of California's Berkeley campus, that great bastion of free speech, unencumbered Unix, and cheap pizza. He joined Hewlett-Packard after graduation and worked for HP for nine years. Cricket began managing the hp.com zone after the Loma Prieta earthquake forcibly transferred the zone's management from HP Labs to HP's Corporate Offices (by cracking a sprinkler main and flooding Labs' computer room). Cricket was firstname.lastname@example.org for over three years, and then joined HP's Professional Services Organization to cofound HP's Internet Consulting Program. Cricket left HP in 1997 to form Acme Byte & Wire, a DNS consulting and training company, with his friend (and now co-author) Matt Larson. Network Solutions acquired Acme in June 2000, and later the same day merged with VeriSign. Cricket worked for a year as Director of DNS Product Management for VeriSign Global Registry Services. Cricket joined Men & Mice, an Icelandic company specializing in DNS software and services, in September, 2001. He is currently their Vice President, Research & Development. Cricket, his wife, Paige, and their son, Walt, live in Colorado with two Siberian Huskies, Annie and Dakota. On warm weekend afternoons, you'll probably find them on the flying trapeze or wakeboarding behind Betty Blue.
Our look is the result of reader comments, our own experimentation, and feedback from distribution channels. Distinctive covers complement our distinctive approach to technical topics, breathing personality and life into potentially dry subjects. The animal on the cover of DNS on Windows 2000 is an African white-necked raven (Corvus albicollis,) a subspecies of raven, the largest of the crow-like birds at about 24 inches long. The sexes look alike; the female is slightly smaller. Perceived as spirited or even impudent, ravens have a distinctive, hoarse, carrying call. They are excellent flyers, hovering and gliding, and are safe in flight from predators. Ravens are scavengers and eat carrion and small live animals, as well as some plants. They sometimes hide and store excess food, and will occasionally carry food in their feet.
African raven nests, built in niches in rocks, are crafted of an underlying stick structure, covered by grass, dirt, and rocks, then smaller twigs with soft materials such as moss or rags, and finally a layer of grass or similar plant material. Ravens lay 3 to 6 mottled grayish-green eggs, and the young hatch after 18 to 20 days of incubation. Both parents (a pair mated for life) will change the nest lining materials to adjust for changes in temperature and climate.
The raven is a popular figure, both profane and sacred, in many legends. Ravens, along with their relatives jays and crows, have long been considered omens of evil in folklore, possibly due to the supposed annual tribute in feathers paid to the Devil; this legend is probably based on the molting of feathers every summer, during which the raven stays relatively well hidden--only this and nothing more. The Old Testament lists ravens among "unclean" birds; ravens also fed Elijah by the brook. Other ancient and medieval cultures considered the raven a symbol of virility or wisdom. An ancient Norse saga describes the use of ravens by ocean navigators as guides to land, and Norse mythology describes ravens as scouts for Odin. Native American folklore tells that the raven created the world and its creatures.
Because it preys on locusts, mice, and rats, the white-necked raven is generally welcomed in Africa (despite the occasional theft of domestic fowl). Like that of many other wild animals, the raven's habitat is dwindling with expansion of the human population. Rachel Wheeler was the production editor and proofreader for DNS onWindows 2000, and Mary Anne Weeks Mayo was the copyeditor. Mary Brad provided quality control, and Sada Preisch, Kimo Carter, and EdieShapiro provided production assistance. Nancy Crumpton wrote the index.
Edie Freedman designed the cover of this book. The cover image is a 19th-century engraving from the Dover Pictorial Archive. Emma Colby produced the cover layout with QuarkXPress 4.1 using Adobe's ITC Garamond font.
Melanie Wang designed the interior layout, based on a series design by David Futato. Anne-Marie Vaduva converted the files from Microsoft Word to FrameMaker 5.5.6 using tools created by Mike Sierra. The text font is Linotype Birka; the heading font is Adobe Myriad Condensed;and the code font is LucasFont's TheSans Mono Condensed. Theillustrations that appear in the book were produced by Robert Romano and Jessamyn Read using Macromedia FreeHand 9 and Adobe Photoshop 6. The tip and warning icons were drawn by Christopher Bing. This colophon was written by Nancy Kotary.
Whenever possible, our books use a durable and flexible lay-flat binding. If the page count exceeds this binding's limit, perfect binding is used.