Published RFCs never change. Although every published RFC has been submitted to careful proofreading by the RFC Editor and the author (s), errors do sometimes go undetected. As a service to the readers of RFCs, this page contains a list of technical and editorial errors that have been reported to the RFC Editor and verified by the authors or the IESG.

In general, we cannot guarantee the correctness of these errata; the reader must make his/her own judgment.
Erratum for RFC 1034

RFC 1034, "Domain names - concepts and facilities", November 1987

Reported By: "Yin Shuming" <yinshuming79@hotmail.com>
Date: Sun, 19 Feb 2006 00:31:58 +0800

UNVERIFIED
Section 4.3.1 says:

 This bit specifies specifies whether the requester wants recursive service 
 for this query. Clients may.....
It should say:
 This bit specifies whether the requester wants recursive service for this 
 query. Clients may.....

Reported By: Chlisin; chlisin_1@sina.com
Date: Fri, 7 Feb 2003 13:56:51 +0800

In Section 3.3: 

    The usual mail address <local-part>@<mail-domain> is mapped into a
    domain name by converting <local-part> into a single label
    (regardles of dots it contains), converting <mail-domain> into a
    domain name using the usual text format for domain names (dots
    denote label breaks), and concatenating the two to form a single
    domain name.
Should be:
    The usual mail address <local-part>@<mail-domain> is mapped into a
    domain name by converting <local-part> into a single label
    (regardless of dots it contains), converting <mail-domain> into a
    domain name using the usual text format for domain names (dots
    denote label breaks), and concatenating the two to form a single
    domain name.