DNS and BIND

Errata for DNS and BIND

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page xvi

The first sentence of the "Quotations" section now reads: "The Lewis Carroll quotations that begin each chapter are from the Millennium Fulcrum Edition 2.9 of the Project Gutenberg electronic text of Alice's Adventures in Wonderland and Through the Looking- Glass." However, the quotations from Through the Looking Glass are actually from the Millennium Fulcrum Edition 1.7 of the Project Gutenberg electronic text.

Anonymous   
Printed
Page iv
Added "Cover Designer: Edie Freedman" under "Production Editor: Ellie

Fountain Maden."

Anonymous    Oct 01, 2000
Printed
Page xvi
Added the following information to the Preface

How to Contact Us We have tested and verified the information in this book to the best of our ability, but you may find that features have changed (or even that we have made mistakes!). Please let us know about any errors you find, as well as your suggestions for future editions, by writing to: O'Reilly & Associates, Inc. 101 Morris Street Sebastopol, CA 95472 1-800-998-9938 (in the U.S. or Canada) 1-707-829-0515 (international/local) 1-707-829-0104 (fax) You can also send us messages electronically. To be put on the mailing list or request a catalog, send email to: info@oreilly.com To ask technical questions or comment on the book, send email to: bookquestions@oreilly.com We have a web site for the book, where we'll list examples, errata, and plans for future editions. You can access this page at: http://www.oreilly.com/catalog/9781565925120/ For more information about this book and others, see the O'Reilly web site: http://www.oreilly.com

Anonymous    Oct 01, 2000
Printed
Page 24
Fig 2-11

Labeled the top dot "ca" and the 1st and 3rd dots in the middle row "bc" and "sk".

Anonymous    Mar 01, 2000
Printed
Page 31

Figure 2-13 did read: 1) Name server A receives a query from the resolver. 2) A queries B. 3) B refers A to other name servers, including C. 4) A queries C. 5) C refers A to other name servers, including D. 6) A queries D. 7) D answers. 8) A returns answer to resolver. Now reads: 1) Name server A receives a recursive query from the resolver. 2) A sends an iterative query to B. 3) B refers A to other name servers, including C. 4) A sends an iterative query to C. 5) C refers A to other name servers, including D. 6) A sends an iterative query to D. 7) D answers. 8) A returns answer to resolver.

Anonymous    Oct 01, 2000
Printed
Page 45

The second sentence in the fourth full paragraph did read: "...for querying the InterNIC's database." Now reads: "...for querying the InterNIC's database (see Figure 3-1)."

Anonymous    Oct 01, 2000
Printed
Page 45

The fifth paragraph did read: "Click on search, and you'll see a screen like Figure 3-1.*" Now reads: "Click on search, and you'll see a screen like Figure 3-2.*"

Anonymous    Oct 01, 2000
Printed
Page 45
In the second to last paragraph, the reference to Figure 3-2 should be

to Figure 3-3.

Anonymous    Oct 01, 2000
Printed
Page 45
In the last paragraph on the page, the reference to Figure 3-3 should

be to Figure 3-4. The last sentence of this paragraph has been deleted.

Anonymous    Oct 01, 2000
Printed
Page 46

The location bar in Figure 3-1 did read: "http://www.internic.net/wp/whois.html" Now reads: "http://www.internic.net/whois.html"

Anonymous    Oct 01, 2000
Printed
Page 49
Figure 3-4 has been replaced with a new screen shot.

Anonymous    Oct 01, 2000
Printed
Page 97

The fifth line of the 1st paragraph did read: "...in which the preference value is higher..." Now reads: "...in which the preference value is equal or higher..."

Anonymous    Oct 01, 2000
Printed
Page 101
"...vanilla DNS 8.1.2 resolver..."

"..the behavior of the 8.1.2 DNS resolver..."

Anonymous    May 01, 1999
Printed
Page 102
"(those before DNS 4.9.3)"

Anonymous    May 01, 1999
Printed
Page 103
"...from DNS 4.8.3 to DNS 4.9."

"...DNS 8..." "...including DNS 8.1.2," "With any DNS resolver..." (should be "With any BIND resolver...") "The DNS 4.8.3 search list" (title) "With DNS 4.8.3 resolvers," "...nearly identical to the DNS 4.9 resolver." (footnote) "One reason older DNS resolvers..." (footnote)

Anonymous    May 01, 1999
Printed
Page 104
"The DNS 4.9 and later search list" (title)

"With DNS 4.9..." "In DNS 4.8.3..."

Anonymous    May 01, 1999
Printed
Page 105
"On the other hand, on a DNS 4.8.3 resolver..."

"...update your resolver to DNS version 4.9 or later..." (note) "For example, under DNS 4.9 or DNS 8..." (note)

Anonymous    May 01, 1999
Printed
Page 106
All of "BIND Operations Guide" is now italicized

"However, since name servers before DNS 4.9..." "...that can cause problems with DNS..."

Anonymous    May 01, 1999
Printed
Page 108
"Note that this is how DNS version 4.9 and later behave."

"The behavior of older version of DNS..."

Anonymous    May 01, 1999
Printed
Page 109
"The sortlist directive is a mechanism in DNS 4.9..."

"The options directive was introduced with DNS 4.9..."

Anonymous    May 01, 1999
Printed
Page 110
"Also introduced with DNS 4.9 resolvers,"

"If you're just moving to a DNS 4.9.3 or 4.9.4 resolver,"

Anonymous    May 01, 1999
Printed
Page 112
"A good implementation of the DNS named..."

Anonymous    May 01, 1999
Printed
Page 116
"Luckily, DNS..."

Anonymous    May 01, 1999
Printed
Page 117
"...as different from that of standard DNS..."

Anonymous    May 01, 1999
Printed
Page 118
"...in the newest DNS distribution."

"...based on DNS 4.8.1." "...installing the DNS 8.1.2 resolver routines..." "...based on the DNS 4.8.3 resolver."

Anonymous    May 01, 1999
Printed
Page 119
"...is based on DNS 4.8.1."

"...doesn't work quite the same way it does with DNS;"

Anonymous    May 01, 1999
Printed
Page 120
"...just as vanilla DNS does."

"...is based on the DNS 4.8.3 resolver,"

Anonymous    May 01, 1999
Printed
Page 121
"...is based on the DNS 4.9.3 resolver,"

"...update Solaris 2.5 and 2.5.1 to DNS 4.9.3..."

Anonymous    May 01, 1999
Printed
Page 122
"...straight DNS;"

"...are based on DNS 4.8.3,"

Anonymous    May 01, 1999
Printed
Page 123
"...is based on DNS 4.9.3...to DNS 4.9.6."

"...also supports the DNS 4.9.3 search list..." "...is based on DNS 4.9.3..." "...were based on DNS 4.8.3..."

Anonymous    May 01, 1999
Printed
Page 124
"...based on the DNS 4.8.1 resolver..."

"...is based on the DNS 4.9.3 resolver."

Anonymous    May 01, 1999
Printed
Page 125
"...has a DNS 4.9.3 name server"

"...to bring the server up to DNS 4.9.4."

Anonymous    May 01, 1999
Printed
Page 126
"...based on the DNS 4.9.2 resolver."

"...ships with a DNS 4.9.6 resolver..." "...is in turn based on DNS 4.8.3."

Anonymous    May 01, 1999
Printed
Page 128
Removed the last paragraph before heading "Windows NT".

Anonymous    Mar 01, 2000
Printed
Page 147
The eighth line down now reads: "Here is an example how to change its

location." Should read: "Here is an example of how to change its location."

Anonymous   
Printed
Page 184 & 185
The root zone . should have quotes around it, "."

zone . { type hint; file "db.cache"; }; It now reads: zone "." { type hint; file "db.cache"; };

Anonymous    May 01, 1999
Printed
Page 185

The 18th line of code on the page did read: zone "0.0.127.in-addr.arpa"; Now reads: zone "0.0.127.in-addr.arpa" {

Anonymous    Oct 01, 2000
Printed
Page 210

In "Contents of file named.conf;" where it reads: zone "0.0.127.in-addr.arpa" { type slave; file "db.127.0.0"; masters { 192.253.254.2;}; }; It now reads: zone "0.0.127.in-addr.arpa" { type master; file "db.127.0.0"; }; to match the named.boot that follows.

Anonymous    May 01, 1999
Printed
Page 214

The "Contents of file named.conf;" where it read: zone "movie.edu" { type slave; file "db.movie"; }; now reads: zone "movie.edu" { type slave; file "db.movie"; masters { 192.249.249.3;}; }; to match the named.boot that follows and also because one must specify a master, at least when configuring a slave zone.

Anonymous    May 01, 1999
Printed
Page 214
Line 9 of code

Added a semicolon to the end of this line; now reads: masters { 192.249.249.3;};

Anonymous    Mar 01, 2000
Printed
Page 214
named.conf example: Changed the zone statement for movie.edu to read:

zone "movie.edu" { type slave; masters { 192.249.249.3; }; file "db.movie"; };

Anonymous    Oct 01, 2000
Printed
Page 217
Solution 3: Changed 254.253.192.in-addr.arpa.dns to

db.192.253.254.

Anonymous    May 01, 1999
Printed
Page 231
NOTIFY example: Changed the also-notify substatement in the

example to read: also-notify { 15.255.152.4; };

Anonymous    May 01, 1999
Printed
Page 246

The second line of the second code sample now reads: options forward only Should read: options forward-only

Anonymous   
Printed
Page 246-247

The options statements now reads: options { forwarders { 192.249.249.1; 192.249.249.3; }; forward only; }; Note the lack of a dash.

Anonymous    May 01, 1999
Printed
Page 246
In the section titled "A More Restricted Name Server," the second code

section did read: forwarders 192.249.249.1 192.249.249.3 options forward-only Now reads: forwarders 192.249.249.1 192.249.249.3 options forward only

Anonymous    Oct 01, 2000
Printed
Page 252
Suggestion for improvement (**NOTE: This is being addressed in the next

edition**): I was unware that the order of statements in named.conf was important when reading Chapter 10. I think the book should have an example where a named ACL is used with the "allow-transfer" statement in "options". (perhaps near page 252). For example, the following will fail, because the "oreilly" ACL has not been defined before it is encountered in the options statment: options { directory "/var/named"; allow-transfer { oreilly; }; }; acl "oreilly" { { 204.148.40/22; }; }; % tail /var/log/named named[4796]: /var/named/named.conf:13: unknown ACL 'oreilly' I think book only shows IPs being used in "allow-transfer," which doesn't trigger this problem.

Anonymous   
Printed
Page 257
In the first named.conf example, on the upper half of the page

The seventh line down did read: "allow-query { any };" Now reads: "allow-query { any; };

Anonymous    Oct 01, 2000
Printed
Page 299
Chapter opening quote

"he was going a journey" should be "he was going on a journey"

Anonymous   
Printed
Page 374

The sixth line of the 1st paragraph now reads: "alias or a canonical name..." Should read: "alias or a canonical (official) name..." {Appendix A} All instances of "class ttl" should be changed to "ttl class". While <rr> contents can take either of the following forms: [<TTL>] [<class>] <type> <RDATA> [<class>] [<TTL>] <type> <RDATA> we use the first form in the book's examples and should be consistent in the appendix.

Anonymous   
Printed
Page 381
sidebar, code line 1,

options { query-source * port 53;}; now reads options { query-source address * port 53;};

Anonymous    Dec 01, 1998
Printed
Page 381

Changed the second example to read: options { query-source address 192.249.249.1 port *; };

Anonymous    May 01, 1999
Printed
Page 381
In Sidebar

Changed 2nd code to read: options { query-source address 192.249.249.1 port *;};

Anonymous    Mar 01, 2000
Printed
Page 406
para. 5, line 2: "http://www.kei.com/homepages/ckd/dns-loc"

changed to "http://www.ckdhr.com/dns-loc/" (the old URL works, but the new URL is more permanent.)

Anonymous    Oct 01, 1998
Printed
Page 419
NS name server

(From RFC 1035, page 18) Binary Representation: NS type code: 1 It now reads: NS type code: 2

Anonymous    May 01, 1999
Printed
Page 464
Zone statement, type hint. Changed the second zone statement to

begin: zone "." [ ( in | hs | hesiod | chaos ) ]

Anonymous    May 01, 1999