Named Error Codes

Mark Olbert mark at arcabama.com
Mon Oct 18 18:40:10 UTC 1999


On 18 Oct 1999 08:27:04 -0700, Barry Margolin <barmar at bbnplanet.com>
wrote:

>RFC 1035 documents the following DNS response codes (NXDOMAIN is the usual
>abbreviation for "Name Error", the rest have pretty obvious mappings to the
>common abbreviations):
>
>RCODE           Response code - this 4 bit field is set as part of
>                responses.  The values have the following
>                interpretation:
>
>                0               No error condition
>
>                1               Format error - The name server was
>                                unable to interpret the query.
>
>                2               Server failure - The name server was
>                                unable to process this query due to a
>                                problem with the name server.
>
>                3               Name Error - Meaningful only for
>                                responses from an authoritative name
>                                server, this code signifies that the
>                                domain name referenced in the query does
>                                not exist.
>
>                4               Not Implemented - The name server does
>                                not support the requested kind of query.
>
>                5               Refused - The name server refuses to
>                                perform the specified operation for
>                                policy reasons.  For example, a name
>                                server may not wish to provide the
>                                information to the particular requester,
>                                or a name server may not wish to perform
>                                a particular operation (e.g., zone
>                                transfer) for particular data.
>
>                6-15            Reserved for future use.

Barry,

Thanx for the reply. I've read the relevant section in RFC 1035, but
when I try to parse the 413 error code I don't get a sensible answer:

decimal 413 = 0000 0001 1001 1101

Am I looking in the wrong place?

- Mark


More information about the bind-users mailing list