Errata

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.

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 97
At the end of the 4th paragraph, the line that reads "...and it finds

itself as the most preferred mail exchanger..." should qualify that by adding
"for the domain" and reiterate that this preference is specified by the holder
of the domain in the email's "to" field, not by the holder of the mail
exchanger's domain.

Anonymous   
Printed Page 98
The first sentence of the second paragraph now reads:

"What happens if a mailer finds itself at the highest preference..."

Should read:

"What happens if a mailer not configured to process a piece of mail
finds itself at the highest preference..."

Anonymous   
Printed Page 98
The last paragraph states that "Many versions of sendmail use class w

or fileclass w as the list of 'local' destinations." This won't make sense to
people unfamiliar with sendmail--is it possible to add a reference for further
information on sendmail, preferably on the Web, to this paragraph?

Anonymous   
Printed Page 231
(at the end of the "DNS NOTIFY (Zone Change Notification)" section

of Chapter 10), an example appears that reads:

zone "acmebw.com" {
type master;
file "db.acmebw.com";
notify yes;
also-notify 15.255.152.4;
};

The above syntax for the "also-notify" clause is incorrect, at least under
BIND 8. The syntax should be:

zone "acmebw.com" {
type master;
file "db.acmebw.com";
notify yes;
also-notify { 15.255.152.4 };
};

(Note the use of the {} characters around the IP number used in the
also-notify substatement.)

The authors should, of course, check this for themselves. But I spent quite
a bit of time recently trying to get the also-notify clause to work with my
BIND 8 server until I thought to try the {} syntax. Which makes sense since
nearly every other BIND element that can accept a parameter list does so by
using {}'s.

Anonymous