1 - 4 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
class
Click on the red underlined text to get to the source
... | TYPE |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| CLASS |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TTL ...
... CLASS ...
... 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. ...
... CLASS values ...
...
CLASS fields appear in resource records. The following CLASS mnemonics
and values are defined:
...
... 2 the CSNET class (Obsolete - used only for examples in
some obsolete RFCs) ...
... 3 the CHAOS class ...
... QCLASS fields appear in the question section of a query. QCLASS values
are a superset of CLASS values; every CLASS is a valid QCLASS. In
...
... query. QCLASS values
are a superset of CLASS values; every CLASS is a valid QCLASS. In
addition to CLASS ...
... 255 any class ...
... The following RR definitions are expected to occur, at least
potentially, in all classes. In particular, NS, SOA, CNAME, and PTR
...
... NS, SOA, CNAME, and PTR
will be used in all classes, and have the same format in all classes.
Because their RDATA format ...
... CNAME, and PTR
will be used in all classes, and have the same format in all classes.
Because their RDATA format is known, all domain ...
... domain-name> which specifies a host which should be
authoritative for the specified class and domain. ...
... states that the named host should be expected to have a zone
starting at owner name of the specified class. Note that the class may
not indicate the protocol family which should be used to communicate
...
... should be expected to have a zone
starting at owner name of the specified class. Note that the class may
not indicate the protocol family which should be used to communicate
with the host ...
... which are name servers for either Internet (IN) or Hesiod (HS)
class information are normally queried using IN class protocols.
...
... location and
Internet address to host mapping. Other classes may employ a similar
strategy in other domains. The intent of this domain ...
... Defining new types, classes, and special namespaces ...
...
The previously defined types and classes are the ones in use as of the
date of this memo. New definitions should be expected. This section
makes some recommendations to designers considering additions to the
...
... for some totally new object. Designers should attempt to define
types and their RDATA formats that are generally applicable to all
classes, and which avoid duplication of information. New classes are
appropriate when the DNS ...
... types and their RDATA formats that are generally applicable to all
classes, and which avoid duplication of information. New classes are
appropriate when the DNS is to be used for a new protocol ...
... DNS is to be used for a new protocol, etc which
requires new class-specific data formats, or when a copy of the existing
name space is desired, but a separate ...
...
New types and classes need mnemonics for master files; the format of the
master files requires that the mnemonics ...
... mnemonics for master files; the format of the
master files requires that the mnemonics for type and class be disjoint.
...
...
TYPE and CLASS values must be a proper subset of QTYPEs and QCLASSes
respectively.
...
... . These fields are a query type (QTYPE), a
query class (QCLASS), and a query domain name (QNAME). The last three
...
... | TYPE |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| CLASS |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TTL ...
... CLASS ...
... 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 ...
... CLASS of the resource record.
For example, the if the TYPE is A and the CLASS is IN,
the RDATA ...
... Pointers can only be used for occurances of a domain name where the
format is not class specific. If this were not the case, a name server
or resolver would be required to know the format of all RRs ...
... The RR begins with optional TTL and class fields, followed by a type and
RDATA field appropriate to the type and class. ...
... and class fields, followed by a type and
RDATA field appropriate to the type and class. Class and type use the
standard mnemonics ...
... fields, followed by a type and
RDATA field appropriate to the type and class. Class and type use the
standard mnemonics, TTL ...
... mnemonics, TTL is a decimal integer. Omitted class and TTL
values are default to the last explicitly stated values. Since type and
class ...
... . Omitted class and TTL
values are default to the last explicitly stated values. Since type and
class mnemonics are disjoint, the parse is unique. (Note that this
order is different from the order used in examples and the order used in
...
... When processing queries with QCLASS=*, or some other QCLASS which
matches multiple classes, the response should never be authoritative
unless the server can guarantee that the response covers all classes.
...
... matches multiple classes, the response should never be authoritative
unless the server can guarantee that the response covers all classes.
...
... RRs at a specific name which match a specific QTYPE and QCLASS.
Where possible, the QTYPE and QCLASS should correspond to a single type
and a single class, because this makes the use of cached data much
simpler. The reason for this is that the presence of data of one type
in a cache ...