Errors in the first printing of "The Concise Guide to DNS and BIND". Discovery/reported dates in dd/mm/yyyy format. Spelling errors throughout the book: - "walruss" should be "walrus" p 2: Fourth paragraph: The correct expansion of BIND is "Berkeley Internet Name Domain". (Thanks Kevin J. Dunlap, 1/12/2000) p 7: Third line, "left to right" should be "right to left" (Thanks to Abhijit Menon-Sen, 2/1/2001) p 9: Second paragraph "nauseum" should be spelled "nauseam". p 11: Second paragraph, last sentence, the reverse address should be "66.222.240.129.in-addr.arpa". A "2" was forgotten. (AMS, 2/1/2001) p 11: Third paragraph: "with each address octet in reverse order" should read "with the address octets in reverse order" (AMS, 2/1/2001) p 12: Second last sentence before the heading should start "But", not "Instead,". (7/12/2000) p 23: Before "named.conf" heading. Right filename is "caching.tgz" not "caching.tar.gz", due to a technical limitation of the publishers web server. (7/12/2000) p 23: Last sentence, before listing, should read "Put this in the right place:" (7/12/2000) p 24: First sentence, strike "in named.conf". (7/12/2000) p 24: Second sentence should start "Because no default exists, ..." (7/12/2000) p 32: "Search" heading, second last paragraph replace with "The number of allowed characters in a search line, and the number of domains you may specify, varies between implementations". (AMS, 2/1/2001) p 34: Last sentence before "A Forward Zone", right filename is "penguin.tgz" not "penguin.tar.gz". (7/12/2000) p 35: The first paragraph after the listing should read, in it's entirety: "There are three mandatory bits in a zone file, all shown above. The $TTL line, the SOA RR and the NS RR for the zone." (7/12/2000) p 36: Second paragraph, second sentence should end "by incrementing it." (7/12/2000) p 37: Second paragraph should read " You can override the TTL for each record. In the above example the SOA records TTL has been overridden to 3,600 seconds, one hour." (10/1/2001) p 48: Second paragraph should read: "Note that RFC 2317 uses a slash (/) as used in CIDR subnet-bitmasks for the CNAME record names. The use of slash here is allowed, but because it is illegal in some contexts some discourage its use. The scheme shown in the previous code, start-end, is one of the legal alternatives." (8/12/2000) p 48: Last paragraph, the first range of numbers, "1-126" should be "1-127". (8/12/2000) p 55: Third paragraph: In the last sentence, replace "old updated A records" with "old A records". (8/12/2000) p 58: Second last paragraph, first sentence should read: "The way to set up this is un-exciting." (Thanks to Toffer) (10/1/2001) p 60: The 4th paragraph contains "