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 1035

RFC 1035, "Domain names - implementation and specification", November 1987

Reported By: "Prentice, Allan Edward (LP & Manpages)" <allan.prentice@hp.com>
Date: Sat, 4 Mar 2006 12:52:37 -0800

UNVERIFIED
Section 5.1 says:

 Because these files are text files several special encodings are
necessary to allow arbitrary data to be loaded. In particular:

of the root.

@ A free standing @ is used to denote the current origin.
It should say:
 Because these files are text files several special encodings are
necessary to allow arbitrary data to be loaded. In particular:

@ A free standing @ is used to denote the current origin.
Rationale:
"of the root." makes no sense here.

Reported By: chlisin_1@sina.com
Date: Mon 10 Feb 2003 15:05:33 +0800

In Section 6.4.2:

                          +-----------------------------------------+
Header | OPCODE=RESPONSE, ID=997 |
+-----------------------------------------+
Question |QTYPE=A, QCLASS=IN, QNAME=VENERA.ISI.EDU |
+-----------------------------------------+
Answer | VENERA.ISI.EDU A IN 10.1.0.52 |
+-----------------------------------------+
Authority | <empty> |
+-----------------------------------------+
Additional | <empty> |
+-----------------------------------------+

There is an error in the Header line. It should be
"OPCODE=IQUERY, ID=997, QR=1" because the OPCODE does not have a
value of RESPONSE (see Section 4.1.1).