Lines Matching refs:rrclass

193    responders may have records with that name, rrtype, and rrclass, and
197    that name, rrtype, and rrclass are conceptually under the control
200    rrclass. Before claiming ownership of a unique resource record set,
957    (unless the qtype is "ANY"), and the record rrclass must match the
995    has previously verified that the name, rrtype and rrclass are unique
1261    its unique resource record set name, rrtype and rrclass cannot
1322    "lexicographically later". If the rrtype and rrclass both match then
1412    Response with the most significant bit of the rrclass set to one.
1413    The most significant bit of the rrclass for a record in the Answer
1493    rrclass, but inconsistent rdata. What may be considered inconsistent
1614    resource record with the same name, rrtype and rrclass as one of A's
1634    resource record with the same name, rrtype and rrclass as one of A's
1660    rrclass and rdata, but an RR TTL of zero. This has the effect of
1688    to be unique, the host sets the most significant bit of the rrclass
1692    previous records with the same name, rrtype and rrclass, all old
1704    name/rrtype/rrclass is no longer valid".
1762    Section of a Multicast DNS packet. The top bit of the rrclass field
1769    an mDNS packet (the field conventionally referred to as the rrclass
1772    0x8001. The value 0x8001 in the rrclass field of a resource record in
2533 20.13 Repurposing of top bit of rrclass in Answer Section
2536    rrclass field is used to indicate that the record is a member of a
2639    * defines a "unicast response" bit in the rrclass of query questions
2640    * defines a "cache flush" bit in the rrclass of response answers
2863    The re-use of the top bit of the rrclass field in the Question and