class
Click on the red underlined text to get to the source
... continuously proposing, implementing and experimenting with new data
types, query types, classes, functions, etc. Thus while the components
of the official protocol are expected to stay essentially unchanged and
operate as a production service ...
... The DNS tags all data with a class as well as the type, so
that we can allow parallel use of different formats for data
of type address ...
... class ...
...
This memo uses the following classes:
...
... which is the type and sometimes class dependent data
which describes the resource: ...
... . The remaining
RR parts are the fixed header (type, class, TTL) which is consistent for
all RRs ...
... integer before
the type field. In order to avoid ambiguity in parsing, type and class
mnemonics are disjoint, TTLs are integers, and the type ...
... mnemonic is
always last. The IN class and TTL values are often omitted from examples
in the interests of clarity.
...
... domain name, it checks to see if the resource set consists of a CNAME
record with a matching class. If so, the name server includes the CNAME
...
... query type
(QTYPE), and query class (QCLASS) and asks for RRs which match. This
type of query ...
... QTYPE and QCLASS fields are each 16 bits long, and are a superset of
defined types and classes.
...
... <any class> ...
... authority. Since a particular name server may not know all of
the classes available in the domain system, it can never know if it is
authoritative for all classes ...
... classes available in the domain system, it can never know if it is
authoritative for all classes. Hence responses to QCLASS=* queries can
never be authoritative.
...
... The domain database is partitioned in two ways: by class, and by "cuts"
made in the name space between nodes ...
... class partition is simple. The database for any class is organized,
delegated, and maintained separately from all other classes. Since, by
...
... database for any class is organized,
delegated, and maintained separately from all other classes. Since, by
convention, the name spaces are the same for all classes, the separate
...
... delegated, and maintained separately from all other classes. Since, by
convention, the name spaces are the same for all classes, the separate
classes can be thought of as an array of parallel namespace ...
... . Since, by
convention, the name spaces are the same for all classes, the separate
classes can be thought of as an array of parallel namespace trees. Note
...
... that the data attached to nodes will be different for these different
parallel classes. The most common reasons for creating a new class are
the necessity for a new data format ...
... nodes will be different for these different
parallel classes. The most common reasons for creating a new class are
the necessity for a new data format for existing types or a desire for a
...
... names in the connected region. Note that the "cuts" in the name space
may be in different places for different classes, the name servers may
be different, etc.
...
... 1035std13]. The query contains a QTYPE, QCLASS,
and QNAME, which describe the types and classes of desired information
and the name of interest.
...
... , MIL, and EDU domains of the IN
class, and would have zones for these domains. The zone data for the
root domain might be:
...
... RR and ")" to show the end of a multi-line RR.
Since the class of all RRs in a zone must be the same, only the first RR
...
... RRs in a zone must be the same, only the first RR
in a zone need specify the class. When a name server loads a zone, it
forces the ...