The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 21
1st paragraph |
This is in the section that discusses IP addresses in the chapter that
describes TCP/IP. The author says that a Class A network has 1.6 million
available addresses, when it's really 16 million addresses.
|
Anonymous |
|
| Printed |
Page 24
I'm not really sure if I've found something or not. On page 24, the |
"network" and "gateway" columns refer to non-existant machines (machine
numbers) in Figure 2-2. I like the book very much and have almost
completed the first reading.
|
Anonymous |
|
| Printed |
Page 24
The diagram on p. 24 describes machines bunched in three |
Ethernet groups, with TCP/IP numberings given for each connection.
An example routing table is also given for one of the machines.
However, if I've got enough of a grip on the material here :),
the router table entry for 149.76.2.0 should be given as gateway
149.76.1.1 (rather than 1.2), and a table entry for 149.76.12.0
should be given as well (to gateway 149.76.1.12), in order for the
table to work with the system as diagrammed.
{85 amd 92} Example 6-2 and Example 6-6:
Chapter 6, "Name Service and Resolver Configuration" describes setting up
BIND for the fictitions domain vbrew.com. In chapter 5 vbrew.com's class
B network ip address is given as 172.16. Yet in Example 6-2, p. 85, the
named.boot file gives the named.rev domain as 72.191.in-addr.arpa. From
my understanding of the text I expected that address to be
16.172.in-addr.arpa, in which case the last line in the example should be
primary 16.172.in-addr.arpa named.rev
rather than
primary 72.191.in-addr.arpa named.rev
Where did the ip address 191.72.0.0, which also appears in Example 6-6 on
page 92, come from?
I'm puzzled by another entry in Example 6-6. The entry for ip address
fragment 1.2 under the winery Ethernet is
1.2 IN PTR vlager-if1.vbrew.com.
I suspect it should be
1.2 IN PTR vlager-if2.vbrew.com.
|
Anonymous |
|
| Printed |
Page 91
In example 6-4, should there be a period after localhost? |
I'm trying to set up named based on this example,
and my version, 4.9.7, does not like it and emits this error
into the messages file:
pri.brushwithscience.com:5: data "localhost" outside zone
"brushwithscience.com" (ignored)
When I take the period out it does not complain.
|
Anonymous |
|
| Printed |
Page 129
The text refers to RFC 1340. That has been superceded by RFC 1700. |
If you ever reprint the book, it would be nice to update that reference.
|
Anonymous |
|