Errata for DNS & Bind Cookbook
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 4
Lower half of page |
It is referred to "tld.whois-server.net", but it should say "tld.whois-servers.
net".
|
Anonymous |
|
Apr 22, 2011 |
Printed |
Page 27
2nd paragraph and a few lines down |
10 IN PTR host.foo.example.
NOW READS:
1 IN PTR host.foo.example.
|
Anonymous |
|
Jul 01, 2004 |
Printed |
Page 32
1st line |
"If the name server at 10.0.0.1 were to crash,",
NOW READS:
"If the web server . . . ."
|
Anonymous |
|
Jul 01, 2004 |
Printed |
Page 41
Lines 1-10 |
Why bother to reduce the TTL of the old PTR record? It is not necessary to change the
old PTR record when moving a host. It is a good idea to clean up afterwards, but
there's no need to change the TTL really.
|
Anonymous |
|
|
Printed |
Page 42
next to last paragraph, 2nd line |
"So iif you leave out explicit records for"
NOW READS:
"So if you leave out explicit records for"
|
Anonymous |
|
Jul 01, 2004 |
Printed |
Page 48
2nd paragraph |
"This chapter shows how to put those configuration statements and substatements
together in sensible ways to produce useful results, like by differentiating the
responses a name server gives out based on the querier's IP address (Recipe 3.17)."
NOW READS:
"...produce useful results, like differentiating the responses a name server gives..."
(remove the "by")
|
Anonymous |
|
Jul 01, 2004 |
Printed |
Page 62
in the See Also section |
Recipes Section 3.20 and Section 3.21, for information on how to send dynamic updates using nsupdate;
NOW READS:
Recipes Section 5.20 and Section 5.21, for information on how to send dynamic updates using nsupdate;
|
Anonymous |
|
Jul 01, 2004 |
Printed |
Page 97
Bottom line |
According to the text in the book you can use "rndc exec" to restart the nameserver.
As far as I know, the "exec"-command is for BIND8 only, so it should probably be "ndc
exec" instead of using the BIND9-only "rndc" command.
|
Anonymous |
|
Apr 22, 2011 |
Printed |
Page 143
Lower half, command-listing |
One of the commands to setup a chroot()-environment on FreeBSD is:
mkdir -p dev etc/namedb var/run etc/namedb is the working directory
I think that the last part ("etc/namedb is the working directory") should probably be
a comment and not part of the command itself?
|
Anonymous |
|
|
Printed |
Page 178
7 lines from the bottom |
the syntax for updates has changed. This code in the example:
$update->push("update", rr_add("$host. 86400 A $addr"));
should be replaced by this:
$update->push(update => rr_add("$host. 86400 A $addr"));
|
Anonymous |
|
Apr 22, 2011 |
Printed |
Page 207
index |
entry for "Conrad, Lee" NOW READS "Conrad, Len"
|
Anonymous |
|
Jul 01, 2004 |
Printed |
Page 212
index |
entry for "rchroot() environment" should be "chroot() environment"
|
Anonymous |
|
Apr 22, 2011 |
|
|