RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 12 records.

Status: Verified (3)

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

Source of RFC: Legacy
Area Assignment: int

Errata ID: 562
Status: Verified
Type: Technical

Reported By: CFeng
Date Reported: 2003-02-09

Section 6.4.2 says:

                         +-----------------------------------------+
           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>                 |
                         +-----------------------------------------+

It should say:

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

Notes:

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).

Errata ID: 2130
Status: Verified
Type: Technical

Reported By: Alexei A. Smekalkine
Date Reported: 2010-04-05
Verifier Name: Brian Haberman
Date Verified: 2012-04-26

Section 3.2.1 says:

TTL             a 32 bit signed integer that specifies the time interval
                that the resource record may be cached before the source
                of the information should again be consulted.  Zero
                values are interpreted to mean that the RR can only be
                used for the transaction in progress, and should not be
                cached.  For example, SOA records are always distributed
                with a zero TTL to prohibit caching.  Zero values can
                also be used for extremely volatile data.

It should say:

TTL             a 32 bit unsigned integer that specifies the time interval
                that the resource record may be cached before the source
                of the information should again be consulted.  Zero
                values are interpreted to mean that the RR can only be
                used for the transaction in progress, and should not be
                cached.  For example, SOA records are always distributed
                with a zero TTL to prohibit caching.  Zero values can
                also be used for extremely volatile data.

Notes:

Conflicting descriptions of the type of TTL field.

Section 3.2.1 says "a 32 bit signed integer" while section 4.1.3 says "a 32 bit unsigned integer".

Errata ID: 563
Status: Verified
Type: Editorial

Reported By: Allan Edward Prentice
Date Reported: 2006-03-04
Verifier Name: Brian Haberman
Date Verified: 2012-04-26

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.

Notes:

"of the root." makes no sense here.

Status: Held for Document Update (8)

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

Source of RFC: Legacy
Area Assignment: int

Errata ID: 1813
Status: Held for Document Update
Type: Technical

Reported By: moritzh
Date Reported: 2009-07-19
Held for Document Update by: Brian Haberman

Section 5.3 says:

The following is an example file which might be used to define the
ISI.EDU zone.and is loaded with an origin of ISI.EDU:

@   IN  SOA     VENERA      Action\.domains (
                                 20     ; SERIAL
                                 7200   ; REFRESH
                                 600    ; RETRY
                                 3600000; EXPIRE
                                 60)    ; MINIMUM

        NS      A.ISI.EDU.
        NS      VENERA
        NS      VAXA
        MX      10      VENERA
        MX      20      VAXA

A       A       26.3.0.103

VENERA  A       10.1.0.52
        A       128.9.0.32

VAXA    A       10.2.0.27
        A       128.9.0.33


[...]

Note the use of the \ character in the SOA RR to specify the responsible
person mailbox "Action.domains@E.ISI.EDU".

It should say:

The following is an example file which might be used to define the
ISI.EDU zone.and is loaded with an origin of ISI.EDU:

@   IN  SOA     VENERA      Action\.domains (
                                 20     ; SERIAL
                                 7200   ; REFRESH
                                 600    ; RETRY
                                 3600000; EXPIRE
                                 60)    ; MINIMUM

        NS      A.ISI.EDU.
        NS      VENERA
        NS      VAXA
        MX      10      VENERA
        MX      20      VAXA

A       A       26.3.0.103

VENERA  A       10.1.0.52
        A       128.9.0.32

VAXA    A       10.2.0.27
        A       128.9.0.33


[...]

Note the use of the \ character in the SOA RR to specify the responsible
person mailbox "Action.domains@ISI.EDU".

Notes:

The introductory sentence and the following zone definition both correctly refer to the zone ISI.EDU. But the closing sentence noting the usage of "\." in the mailbox name erroneously expands the example to "Action.domains@E.ISI.EDU" instead of "Action.domains@ISI.EDU".

Errata ID: 3421
Status: Held for Document Update
Type: Technical

Reported By: Jeremy C. Reed
Date Reported: 2012-11-28
Held for Document Update by: Brian Haberman

Section 3.3.5 says:

The recommended policy for dealing with MD RRs found in
a master file is to reject them, or to convert them to MX RRs with a
preference of 10.

It should say:

The recommended policy for dealing with MF RRs found in
a master file is to reject them, or to convert them to MX RRs with a
preference of 10.

Notes:

3.3.5 about MF says "dealing with MD". It should probably say "dealing with MF". I assume this is a copy and paste error from earlier section about MD.

Errata ID: 2646
Status: Held for Document Update
Type: Editorial

Reported By: Nikolai Malykh
Date Reported: 2010-11-29
Held for Document Update by: Brian Haberman

Section 5.3 says:

The following is an example file which might be used to define the
ISI.EDU zone.and is loaded with an origin of ISI.EDU:

It should say:

The following is an example file which might be used to define the
ISI.EDU zone and is loaded with an origin of ISI.EDU:

Errata ID: 2691
Status: Held for Document Update
Type: Editorial

Reported By: Hirochika Asai
Date Reported: 2011-01-22
Held for Document Update by: Brian Haberman

Section 4.1.4 says:

In this scheme, an entire domain name or a list of labels at
the end of a domain name is replaced with a pointer to a prior occurance
of the same name.

It should say:

In this scheme, an entire domain name or a list of labels at
the end of a domain name is replaced with a pointer to a prior occurrence
of the same name.

Errata ID: 3230
Status: Held for Document Update
Type: Editorial

Reported By: Sam Bretheim
Date Reported: 2012-05-22
Held for Document Update by: Brian Haberman

Section 4.1.1 says:

RA              Recursion Available - this be is set or cleared in a

It should say:

RA              Recursion Available - this bit is set or cleared in a

Errata ID: 3691
Status: Held for Document Update
Type: Editorial

Reported By: Sam Bretheim
Date Reported: 2013-08-01
Held for Document Update by: Ted Lemon

Section 5.1 says:

\DDD            where each D is a digit is the octet corresponding to

It should say:

\DDD            where each D is a digit in the octet corresponding to

Errata ID: 4227
Status: Held for Document Update
Type: Editorial

Reported By: Sun Congyou
Date Reported: 2015-01-09
Held for Document Update by: Ted Lemon
Date Held: 2015-01-10

Section 4.2.1 says:

Messages sent using UDP user server port 53 (decimal).

It should say:

Messages sent using UDP use server port 53 (decimal).

Notes:

I'm very sorry for my previous mistake in errata ID 4226, this should be a correct one.

Errata ID: 5463
Status: Held for Document Update
Type: Editorial

Reported By: Shulhan
Date Reported: 2018-08-14
Held for Document Update by: Warren Kumari (Ops AD)
Date Held: 2018-08-14

Section 4.1.3 says:

RDATA           a variable length string of octets that describes the
                resource.  The format of this information varies
                according to the TYPE and CLASS of the resource record.
                For example, the if the TYPE is A and the CLASS is IN,
                the RDATA field is a 4 octet ARPA Internet address.

It should say:

RDATA           a variable length string of octets that describes the
                resource.  The format of this information varies
                according to the TYPE and CLASS of the resource record.
                For example, if the TYPE is A and the CLASS is IN,
                the RDATA field is a 4 octet ARPA Internet address.

Notes:

The original text says "For example, the if the ...", where it should say, "For example, if the ...".

Status: Rejected (1)

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

Source of RFC: Legacy
Area Assignment: int

Errata ID: 4226
Status: Rejected
Type: Editorial

Reported By: Sun Congyou
Date Reported: 2015-01-09
Rejected by: Ted Lemon
Date Rejected: 2015-01-10

Section 4.2.1 says:

Messages sent using UDP user server port 53 (decimal).

It should say:

Messages sent using UDP uses server port 53 (decimal).

Notes:


--VERIFIER NOTES--
Duplicate of errata #4227.

Report New Errata