From: Evan Hunt Date: Mon, 12 Oct 2015 19:45:10 +0000 (-0700) Subject: [master] add link achors to to
tags X-Git-Tag: v9.11.0a1~351 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b2171b164c0780bea7beda2562b922ce3c050322;p=thirdparty%2Fbind9.git [master] add link achors to to
tags --- diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index f494ffbb3a3..6a686593a2e 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -45,7 +45,7 @@ Introduction - + The Internet Domain Name System (DNS) consists of the syntax @@ -57,8 +57,7 @@ hierarchical databases. -
Scope of Document - +
Scope of Document The Berkeley Internet Name Domain @@ -72,8 +71,8 @@
-
Organization of This Document - +
Organization of This Document + In this document, Chapter 1 introduces the basic DNS and BIND concepts. Chapter 2 @@ -100,8 +99,7 @@ System.
-
Conventions Used in This Document - +
Conventions Used in This Document In this document, we use the following general typographic @@ -227,8 +225,8 @@
-
The Domain Name System (<acronym>DNS</acronym>) - +
The Domain Name System (<acronym>DNS</acronym>) + The purpose of this document is to explain the installation and upkeep of the BIND (Berkeley Internet @@ -237,8 +235,7 @@ (DNS) as they relate to BIND. -
DNS Fundamentals - +
DNS Fundamentals The Domain Name System (DNS) is a hierarchical, distributed @@ -260,8 +257,8 @@ from ISC as a separate download. -
Domains and Domain Names - +
+
Domains and Domain Names The data stored in the DNS is identified by domain names that are organized as a tree according to @@ -311,8 +308,8 @@
-
Zones - +
Zones + To properly operate a name server, it is important to understand the difference between a zone @@ -367,8 +364,7 @@
-
Authoritative Name Servers - +
Authoritative Name Servers Each zone is served by at least @@ -386,8 +382,7 @@ dig (). -
The Primary Master - +
The Primary Master The authoritative server where the master copy of the zone @@ -408,8 +403,8 @@
-
Slave Servers - +
Slave Servers + The other authoritative servers, the slave servers (also known as secondary servers) @@ -424,8 +419,7 @@
-
Stealth Servers - +
Stealth Servers Usually all of the zone's authoritative servers are listed in @@ -463,9 +457,7 @@
-
Caching Name Servers - - +
Caching Name Servers
-
Name Server Intensive Environment Issues - +
Name Server Intensive Environment Issues + For name server intensive environments, there are two alternative configurations that may be used. The first is where clients and @@ -638,8 +622,8 @@
-
Supported Operating Systems - +
Supported Operating Systems + ISC BIND 9 compiles and runs on a large number @@ -654,7 +638,7 @@ Name Server Configuration - + In this chapter we provide some suggested configurations along with guidelines for their use. We suggest reasonable values for @@ -662,9 +646,9 @@
Sample Configurations - -
A Caching-only Name Server - + +
A Caching-only Name Server + The following sample configuration is appropriate for a caching-only name server for use by clients internal to a corporation. All @@ -695,8 +679,8 @@ zone "0.0.127.in-addr.arpa" {
-
An Authoritative-only Name Server - +
An Authoritative-only Name Server + This sample configuration is for an authoritative-only server that is the master server for "example.com" @@ -745,8 +729,8 @@ zone "eng.example.com" {
-
Load Balancing - +
Load Balancing + @@ -11958,8 +11879,8 @@ zone zone_name class
-
Class - +
Class + The zone's name may optionally be followed by a class. If a class is not specified, class IN (for Internet), @@ -11980,8 +11901,7 @@ zone zone_name class
-
Zone Options - +
Zone Options @@ -12736,7 +12656,7 @@ example.com. NS ns2.example.net.
Dynamic Update Policies - + BIND 9 supports two alternative methods of granting clients the right to perform dynamic updates to a zone, configured by the @@ -13142,8 +13062,8 @@ example.com. NS ns2.example.net.
-
Multiple views - +
Multiple views + When multiple views are in use, a zone may be referenced by more than one of them. Often, the views @@ -13204,10 +13124,10 @@ view external {
-
Zone File - +
Zone File +
Types of Resource Records and When to Use Them - + This section, largely borrowed from RFC 1034, describes the concept of a Resource Record (RR) and explains when each is used. @@ -13216,7 +13136,6 @@ view external { and implemented in the DNS. These are also included.
Resource Records - A domain name identifies a node. Each node has a set of @@ -14393,8 +14312,8 @@ view external { used as "pointers" to other data in the DNS.
-
Textual expression of RRs - +
Textual expression of RRs + RRs are represented in binary form in the packets of the DNS protocol, and are usually represented in highly encoded form @@ -14594,8 +14513,7 @@ view external {
-
Discussion of MX Records - +
Discussion of MX Records As described above, domain servers store information as a @@ -14778,7 +14696,7 @@ view external {
Setting TTLs - + The time-to-live of the RR field is a 32-bit integer represented in units of seconds, and is primarily used by resolvers when they @@ -14848,8 +14766,8 @@ view external { can be explicitly specified, for example, 1h30m.
-
Inverse Mapping in IPv4 - +
Inverse Mapping in IPv4 + Reverse name resolution (that is, translation from IP address to name) is achieved by means of the in-addr.arpa domain @@ -14907,8 +14825,8 @@ view external {
-
Other Zone File Directives - +
Other Zone File Directives + The Master File Format was initially defined in RFC 1035 and has subsequently been extended. While the Master File Format @@ -14921,8 +14839,8 @@ view external { Master File Directives include $ORIGIN, $INCLUDE, and $TTL. -
The <command>@</command> (at-sign) - +
The <command>@</command> (at-sign) + When used in the label (or name) field, the asperand or at-sign (@) symbol represents the current origin. @@ -14931,8 +14849,8 @@ view external { trailing dot).
-
The <command>$ORIGIN</command> Directive - +
The <command>$ORIGIN</command> Directive + Syntax: $ORIGIN domain-name @@ -14963,8 +14881,8 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
-
The <command>$INCLUDE</command> Directive - +
The <command>$INCLUDE</command> Directive + Syntax: $INCLUDE filename @@ -14997,8 +14915,8 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
-
The <command>$TTL</command> Directive - +
The <command>$TTL</command> Directive + Syntax: $TTL default-ttl @@ -15015,8 +14933,8 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
-
<acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive - +
<acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive + Syntax: $GENERATE range @@ -15217,7 +15135,7 @@ HOST-127.EXAMPLE. MX 0 .
Additional File Formats - + In addition to the standard textual format, BIND 9 supports the ability to read or dump to zone files in @@ -15277,7 +15195,7 @@ HOST-127.EXAMPLE. MX 0 .
BIND9 Statistics - + BIND 9 maintains lots of statistics information and provides several interfaces for users to @@ -15430,7 +15348,7 @@ HOST-127.EXAMPLE. MX 0 .
The Statistics File - + The text format statistics dump begins with a line, like: @@ -15469,7 +15387,7 @@ HOST-127.EXAMPLE. MX 0 .
Statistics Counters - + The following tables summarize statistics counters that BIND 9 provides. @@ -15487,8 +15405,7 @@ HOST-127.EXAMPLE. MX 0 . BIND 8 statistics, if applicable. -
Name Server Statistics Counters - +
Name Server Statistics Counters @@ -16112,8 +16029,7 @@ HOST-127.EXAMPLE. MX 0 .
-
Zone Maintenance Statistics Counters - +
Zone Maintenance Statistics Counters @@ -16268,8 +16184,7 @@ HOST-127.EXAMPLE. MX 0 .
-
Resolver Statistics Counters - +
Resolver Statistics Counters @@ -16654,8 +16569,7 @@ HOST-127.EXAMPLE. MX 0 .
-
Socket I/O Statistics Counters - +
Socket I/O Statistics Counters Socket I/O statistics counters are defined per socket @@ -16811,8 +16725,9 @@ HOST-127.EXAMPLE. MX 0 .
-
Compatibility with <emphasis>BIND</emphasis> 8 Counters - + +
Compatibility with <emphasis>BIND</emphasis> 8 Counters + Most statistics counters that were available in BIND 8 are also supported in @@ -16869,9 +16784,9 @@ HOST-127.EXAMPLE. MX 0 . <acronym>BIND</acronym> 9 Security Considerations - +
Access Control Lists - + Access Control Lists (ACLs) are address match lists that you can set up and nickname for future use in @@ -17062,8 +16977,8 @@ allow-query { !{ !10/8; any; }; key example; };
-
<command>Chroot</command> and <command>Setuid</command> - +
<command>Chroot</command> and <command>Setuid</command> + On UNIX servers, it is possible to run BIND in a chrooted environment (using @@ -17087,8 +17002,7 @@ allow-query { !{ !10/8; any; }; key example; }; /usr/local/sbin/named -u 202 -t /var/named -
The <command>chroot</command> Environment - +
The <command>chroot</command> Environment In order for a chroot environment @@ -17116,8 +17030,7 @@ allow-query { !{ !10/8; any; }; key example; };
-
Using the <command>setuid</command> Function - +
Using the <command>setuid</command> Function Prior to running the named daemon, @@ -17139,7 +17052,6 @@ allow-query { !{ !10/8; any; }; key example; };
Dynamic Update Security - Access to the dynamic @@ -17185,11 +17097,10 @@ allow-query { !{ !10/8; any; }; key example; }; Troubleshooting - -
Common Problems - + +
Common Problems +
It's not working; how can I figure out what's wrong? - The best solution to solving installation and @@ -17202,7 +17113,6 @@ allow-query { !{ !10/8; any; }; key example; };
Incrementing and Changing the Serial Number - Zone serial numbers are just numbers — they aren't @@ -17231,8 +17141,7 @@ allow-query { !{ !10/8; any; }; key example; };
-
Where Can I Get Help? - +
Where Can I Get Help? The Internet Systems Consortium @@ -17259,118 +17168,111 @@ allow-query { !{ !10/8; any; }; key example; }; Release Notes - A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym> - -
DNS - - Although the "official" beginning of the Domain Name - System occurred in 1984 with the publication of RFC 920, the - core of the new system was described in 1983 in RFCs 882 and - 883. From 1984 to 1987, the ARPAnet (the precursor to today's - Internet) became a testbed of experimentation for developing the - new naming/addressing scheme in a rapidly expanding, - operational network environment. New RFCs were written and - published in 1987 that modified the original documents to - incorporate improvements based on the working model. RFC 1034, - "Domain Names-Concepts and Facilities", and RFC 1035, "Domain - Names-Implementation and Specification" were published and - became the standards upon which all DNS implementations are - built. - - - - The first working domain name server, called "Jeeves", was - written in 1983-84 by Paul Mockapetris for operation on DEC - Tops-20 - machines located at the University of Southern California's - Information - Sciences Institute (USC-ISI) and SRI International's Network - Information - Center (SRI-NIC). A DNS server for - Unix machines, the Berkeley Internet - Name Domain (BIND) package, was - written soon after by a group of - graduate students at the University of California at Berkeley - under - a grant from the US Defense Advanced Research Projects - Administration - (DARPA). - -
+ + Although the "official" beginning of the Domain Name + System occurred in 1984 with the publication of RFC 920, the + core of the new system was described in 1983 in RFCs 882 and + 883. From 1984 to 1987, the ARPAnet (the precursor to today's + Internet) became a testbed of experimentation for developing the + new naming/addressing scheme in a rapidly expanding, + operational network environment. New RFCs were written and + published in 1987 that modified the original documents to + incorporate improvements based on the working model. RFC 1034, + "Domain Names-Concepts and Facilities", and RFC 1035, "Domain + Names-Implementation and Specification" were published and + became the standards upon which all DNS implementations are + built. + -
BIND - - Versions of BIND through - 4.8.3 were maintained by the Computer - Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark - Painter, David Riggle and Songnian Zhou made up the initial BIND - project team. After that, additional work on the software package - was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment - Corporation - employee on loan to the CSRG, worked on BIND for 2 years, from 1985 - to 1987. Many other people also contributed to BIND development - during that time: Doug Kingston, Craig Partridge, Smoot - Carl-Mitchell, - Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently - handled by Mike Karels and Øivind Kure. - - - BIND versions 4.9 and 4.9.1 were - released by Digital Equipment - Corporation (now Compaq Computer Corporation). Paul Vixie, then - a DEC employee, became BIND's - primary caretaker. He was assisted - by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan - Beecher, Andrew - Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat - Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe - Wolfhugel, and others. - - - In 1994, BIND version 4.9.2 was sponsored by - Vixie Enterprises. Paul - Vixie became BIND's principal - architect/programmer. - - - BIND versions from 4.9.3 onward - have been developed and maintained - by the Internet Systems Consortium and its predecessor, - the Internet Software Consortium, with support being provided - by ISC's sponsors. - - - As co-architects/programmers, Bob Halley and - Paul Vixie released the first production-ready version of - BIND version 8 in May 1997. - - - BIND version 9 was released in September 2000 and is a - major rewrite of nearly all aspects of the underlying - BIND architecture. - - - BIND versions 4 and 8 are officially deprecated. - No additional development is done - on BIND version 4 or BIND version 8. - - - BIND development work is made - possible today by the sponsorship - of several corporations, and by the tireless work efforts of - numerous individuals. - -
+ + The first working domain name server, called "Jeeves", was + written in 1983-84 by Paul Mockapetris for operation on DEC + Tops-20 + machines located at the University of Southern California's + Information + Sciences Institute (USC-ISI) and SRI International's Network + Information + Center (SRI-NIC). A DNS server for + Unix machines, the Berkeley Internet + Name Domain (BIND) package, was + written soon after by a group of + graduate students at the University of California at Berkeley + under + a grant from the US Defense Advanced Research Projects + Administration + (DARPA). + + + Versions of BIND through + 4.8.3 were maintained by the Computer + Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark + Painter, David Riggle and Songnian Zhou made up the initial BIND + project team. After that, additional work on the software package + was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment + Corporation + employee on loan to the CSRG, worked on BIND for 2 years, from 1985 + to 1987. Many other people also contributed to BIND development + during that time: Doug Kingston, Craig Partridge, Smoot + Carl-Mitchell, + Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently + handled by Mike Karels and Øivind Kure. + + + BIND versions 4.9 and 4.9.1 were + released by Digital Equipment + Corporation (now Compaq Computer Corporation). Paul Vixie, then + a DEC employee, became BIND's + primary caretaker. He was assisted + by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan + Beecher, Andrew + Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat + Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe + Wolfhugel, and others. + + + In 1994, BIND version 4.9.2 was sponsored by + Vixie Enterprises. Paul + Vixie became BIND's principal + architect/programmer. + + + BIND versions from 4.9.3 onward + have been developed and maintained + by the Internet Systems Consortium and its predecessor, + the Internet Software Consortium, with support being provided + by ISC's sponsors. + + + As co-architects/programmers, Bob Halley and + Paul Vixie released the first production-ready version of + BIND version 8 in May 1997. + + + BIND version 9 was released in September 2000 and is a + major rewrite of nearly all aspects of the underlying + BIND architecture. + + + BIND versions 4 and 8 are officially deprecated. + No additional development is done + on BIND version 4 or BIND version 8. + + + BIND development work is made + possible today by the sponsorship + of several corporations, and by the tireless work efforts of + numerous individuals. + General <acronym>DNS</acronym> Reference Information - +
IPv6 addresses (AAAA) - + IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces which were introduced in the DNS to facilitate @@ -17427,9 +17329,9 @@ allow-query { !{ !10/8; any; }; key example; };
Bibliography (and Suggested Reading) - +
Request for Comments (RFCs) - + Specification documents for the Internet protocol suite, including the DNS, are published as part of @@ -17453,7 +17355,7 @@ allow-query { !{ !10/8; any; }; key example; }; Standards - + RFC974 PartridgeC. @@ -17475,7 +17377,6 @@ allow-query { !{ !10/8; any; }; key example; }; Proposed Standards - RFC2181 @@ -17582,7 +17483,7 @@ allow-query { !{ !10/8; any; }; key example; }; <acronym>DNS</acronym> Security Proposed Standards - + RFC3225 @@ -17640,7 +17541,7 @@ allow-query { !{ !10/8; any; }; key example; }; Other Important RFCs About <acronym>DNS</acronym> Implementation - + RFC1535 GavronE. @@ -17682,7 +17583,7 @@ allow-query { !{ !10/8; any; }; key example; }; Resource Record Types - + RFC1183 @@ -17835,7 +17736,7 @@ allow-query { !{ !10/8; any; }; key example; }; <acronym>DNS</acronym> and the Internet - + RFC1101 MockapetrisP. V. @@ -17886,7 +17787,7 @@ allow-query { !{ !10/8; any; }; key example; }; <acronym>DNS</acronym> Operations - + RFC1033 LottorM. @@ -17928,7 +17829,7 @@ allow-query { !{ !10/8; any; }; key example; }; Internationalized Domain Names - + RFC2825 @@ -17970,7 +17871,7 @@ allow-query { !{ !10/8; any; }; key example; }; Other <acronym>DNS</acronym>-related RFCs - + Note: the following list of RFCs, although @@ -18048,7 +17949,7 @@ allow-query { !{ !10/8; any; }; key example; }; Obsolete and Unimplemented Experimental RFC - + RFC1712 @@ -18081,7 +17982,7 @@ allow-query { !{ !10/8; any; }; key example; }; Obsoleted DNS Security RFCs - + Most of these have been consolidated into RFC4033, @@ -18185,7 +18086,7 @@ allow-query { !{ !10/8; any; }; key example; };
Internet Drafts - + Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs @@ -18197,8 +18098,8 @@ allow-query { !{ !10/8; any; }; key example; }; after which they are deleted unless updated by their authors.
-
Other Documents About <acronym>BIND</acronym> - +
Other Documents About <acronym>BIND</acronym> + @@ -18218,12 +18119,10 @@ allow-query { !{ !10/8; any; }; key example; }; BIND 9 DNS Library Support - Manual pages -