Types of Nameservers 2. Zone Datafiles 2. Resolvers 2. Resolution 2. Root Nameservers 2. Recursion 2. Iteration 2. Choosing Between Authoritative Nameservers 2. The Whole Enchilada 2. Mapping Addresses to Names 2.
Caching 2. Time to Live 3. Where Do I Start? Getting BIND 3. Handy Mailing Lists and Usenet Newsgroups 3. Finding IP Addresses 3. Choosing a Domain Name 3. On Registrars and Registries 3. Where in the World Do I Fit? Back in the U. The generic top-level domains 3. Choosing a registrar 3. Registering Your Zones 4. Our Zone 4. Setting Up Zone Data 4. The Zone Datafiles 4.
Comments 4. SOA Records 4. NS Records 4. Address and Alias Records 4. PTR Records 4. The Completed Zone Datafiles 4. The Loopback Address 4. The Root Hints Data 4. Abbreviations 4. Appending Domain Names 4. The Notation 4. Repeat Last Name 4. The Shortened Zone Datafiles 4.
Hostname Checking 4. Tools 4. BIND 9 Tools 4. Running a Primary Nameserver 4. Starting Up the Nameserver 4. Check for Syslog Errors 4.
Testing Your Setup with nslookup 4. Set the local domain name 4. Look up a local domain name 4. Look up a local address 4. Look up a remote domain name 4. One more test 4. Editing the Startup Files 4.
Running a Slave Nameserver 4. Setup 4. Backup Files 4. SOA Values 4. Multiple Master Servers 4. Adding More Zones 4. DNS and Electronic Mail 5. MX Records 5. The MX Algorithm 5. DNS and Email Authentication 5. The Sender Policy Framework 6. Configuring Hosts 6. The Resolver 6. Resolver Configuration 6. The Local Domain Name 6. The Search List 6. The BIND 4. The search Directive 6. The nameserver Directive 6. One nameserver configured 6.
More than one nameserver configured 6. The sortlist Directive 6. The options Directive 6. Comments 6. A Note on the 4. Sample Resolver Configurations 6.
Resolver Only 6. Local Nameserver 6. Minimizing Pain and Suffering 6. Differences in Service Behavior 6. Electronic Mail 6. Providing Aliases 6. Additional Configuration Files 6. The Windows XP Resolver 6.
Caching 6. Subnet Prioritization 7. Maintaining BIND 7. Controlling the Nameserver 7. Using rndc to control multiple servers 7. New rndc commands 7. Using Signals 7. Updating Zone Datafiles 7. Adding and Deleting Hosts 7. SOA Serial Numbers 7. Starting Over with a New Serial Number 7.
Additional Zone Datafile Entries 7. General text information 7. Responsible Person 7. Generating Zone Datafiles from the Host Table 7. Keeping the Root Hints Current 7. Organizing Your Files 7. Using Several Directories 7. Changing the Origin in a Zone Datafile 7.
Including Other Zone Datafiles 7. Changing System File Locations 7. Logging 7. The logging Statement 7. Channel Details 7. File channels 7. Data formatting for all channels 7. Category Details 7. BIND 8 categories 7. BIND 9 categories 7. Viewing all category messages 7. Keeping Everything Running Smoothly 7. Common Syslog Messages 7.
BIND 8 statistics 7. BIND 9 statistics 7. Using the BIND statistics 8. Growing Your Domain 8. How Many Nameservers? Capacity Planning 8. Adding More Nameservers 8. Primary Master and Slave Servers 8. Caching-Only Servers 8. Partial-Slave Servers 8. Registering Nameservers 8. Changing TTLs 8. Planning for Disasters 8. Outages 8. Recommendations 8. Coping with Disaster 8. Long Outages Days 8. Really Long Outages Weeks 9. Parenting 9. When to Become a Parent 9.
How Many Children? What to Name Your Children 9. How to Become a Parent: Creating Subdomains 9. Creating and Delegating a Subdomain 9. An fx. On the movie.
Delegating an in-addr. Each node in the tree has a text label, which identifies the node relative to its parent. In text, the root node is written as a single dot.
Each node is also the root of a new subtree of the overall tree. Each of these subtrees represents a partition of the overall database—a directory in the Unix filesystem, or a domain in the Domain Name System. Subdomains, like subdirectories, are drawn as children of their parent domains. Every domain has a unique name, like every directory. In DNS, the domain name is the sequence of labels from the node at the root of the domain to the root of the whole tree, with dots.
In DNS, each domain can be broken into a number of subdomains, and responsibility for those subdomains can be doled out to different organizations. Berkeley Figure This is similar to remotely mounting a filesystem: certain directories in a filesystem may actually be filesystems on other hosts, mounted from remote hosts.
Delegating authority for berkeley. Berkeley creates a new zone , an autonomously administered piece of the namespace. The zone berkeley. If cs. Domain names are used as indexes into the DNS database. In a filesystem, directories contain files and subdirectories. Likewise, domains can contain both hosts and subdomains.
Each host on a network has a domain name, which points to information about the host see Figure This information may include IP addresses, information about mail routing, etc. Hosts may also have one or more domain name aliases , which are simply pointers from one domain name the alias to another the official, or canonical , domain name.
In Figure , mailhub. Why all the complicated structure? TXT had. For example, making domain names hierarchical eliminates the pitfall of name collisions. Each domain has a unique domain name, so the organization that runs the domain is free to name hosts and subdomains within its domain. For example, the organization that runs hic. There are other name-resolution mechanisms besides DNS, some of which may be a standard part of your operating system.
Sometimes the overhead involved in managing zones and their nameservers outweighs the benefits. On the other hand, there are circumstances in which you have no other choice but to set up and manage nameservers. Here are some guidelines to help you make that decision:. System V systems require the following tar command instead:. If zcat is not available on your system, use separate uncompress and tar commands. For help using ftpmail , send an email to ftpmail online.
You can access this page at:. We use the following font and format conventions for Unix commands, utilities, and system calls:. Sample interactive sessions, showing command-line input and corresponding output, are shown in constant-width font, with user-supplied input in bold:. If the command must be typed by the superuser root , we use the sharp, or pound sign :.
Domain names, filenames, functions, commands, Unix manpages, Windows features, URLs, and programming elements taken from the code snippets are printed in italics when they appear within a paragraph. This book is here to help you get your job done.
In general, you may use the code in this book in your programs and documentation. For example, writing a program that uses several chunks of code from this book does not require permission. Answering a question by citing this book and quoting example code does not require permission. We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN.
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions oreilly. Robert Elz, and Paul Vixie for their invaluable contributions to this book. For the fourth edition, the authors owe a debt of gratitude to Kevin Dunlap, Edward Lewis, and Brian Wellington, their crack review squad. Cricket would particularly like to thank his former manager, Rick Nordensten, the very model of a modern HP manager, on whose watch the first version of this book was written; his neighbors, who bore his occasional crabbiness for many months; and of course his wife Paige for her unflagging support and for putting up with his tap-tap-tapping during her nap-nap-napping.
For the third edition, Cricket acknowledges a debt of gratitude to his partner, Matt Larson, for his co-development of the Acme Razor. For the fourth edition, Cricket thanks his loyal, furry fans, Dakota and Annie, for kisses and companionship, and wonderful Walter B.
For the fifth edition, he must mention the other new addition, the fabulous Baby G. And he sends his thanks to his friends and colleagues at Infoblox for their hard work, their generous support, and their company. Paul would like to thank his wife, Katherine, for her patience, for many review sessions, and for proving that she could make a quilt in her spare time more quickly than her spouse could write his half of a book. Skip to main content. Start your free trial.
Chapter 1 , Background Provides a little historical perspective and discusses the problems that motivated the development of DNS, then presents an overview of DNS theory. Chapter 3 , Where Do I Start? Chapter 7 , Maintaining BIND Describes the periodic maintenance administrators must perform to keep their zones running smoothly, such as checking nameserver health and authority. Chapter 8 , Growing Your Domain Covers how to plan for the growth and evolution of your zones, including how to get big and how to plan for moves and outages.
Chapter 9 , Parenting Explores the joys of becoming a parent zone. Chapter 11 , Security Describes how to secure your nameserver and how to configure your nameservers to deal with Internet firewalls, and describes two new security enhancements to DNS: the DNS Security Extensions and Transaction Signatures.
Chapter 12 , nslookup and dig Shows the ins and outs of the most popular tools for doing DNS debugging, including techniques for digging obscure information out of remote nameservers. Chapter 16 , Architecture Presents an end-to-end design for DNS infrastructure, including external nameservers, forwarders, and internal nameservers.
Chapter 17 , Miscellaneous Ties up all the loose ends. Appendix E , BIND Nameserver and Resolver Configuration Summarizes the syntax and semantics of each of the parameters available for configuring nameservers and resolvers.
System administrators setting up their first zones Should read Chapters 1 and 2 for DNS theory, Chapter 3 for information on getting started and selecting a good domain name, then Chapters 4 and 5 to learn how to set up a zone for the first time.
Experienced administrators May benefit from reading Chapter 6 to learn how to configure DNS resolvers on different hosts, and Chapter 7 for information on maintaining their zones. System administrators on networks without full Internet connectivity Should read Chapter 5 to learn how to configure mail on such networks, and Chapters 11 and 17 to learn how to set up an independent DNS infrastructure.
Network administrators not directly responsible for any zones Should still read Chapters 1 and 2 for DNS theory, Chapter 12 to learn how to use nslookup and dig , and Chapter 14 for troubleshooting tactics. Obtaining the Example Programs. How to Contact Us. Conventions Used in This Book. Tip This icon signifies a tip, suggestion, or general note.
0コメント