Lines Matching refs:rrclass

217    responders may have records with that name, rrtype, and rrclass, and
221    name, rrtype, and rrclass are under the control or ownership of a
872    (unless the qtype is "ANY"), and the record rrclass must match the
923    verified that the requested name, rrtype and rrclass in the DNS query
1113    its unique resource record set name, rrtype and rrclass cannot
1160    'lexicographically later'. If the rrtype and rrclass both match then
1215    Response with the most significant bit of the rrclass set to one.
1216    The most significant bit of the rrclass for a record in the Answer
1278    and rrclass, but inconsistent rdata. What may be considered
1389    resource record with the same name, rrtype and rrclass as one of A's
1402    resource record with the same name, rrtype and rrclass as one of A's
1428    rrclass and rdata, but an RR TTL of zero. This has the effect of
1475    to be unique, the host sets the most significant bit of the rrclass
1479    previous records with the same name, rrtype and rrclass, all old
1491    name/rrtype/rrclass is no longer valid".
1549    Section of a Multicast DNS packet. The top bit of the rrclass field
1556    an mDNS packet (the field conventionally referred to as the rrclass
1566    0x8001. The value 0x8001 in the rrclass field of a resource record in
2165 19.12. Repurposing of top bit of rrclass in Answer Section
2168    rrclass field is used to indicate that the record is a member of a
2257    * defines a "unicast response" bit in the rrclass of query questions
2258    * defines a "cache flush" bit in the rrclass of response answers
2454    The re-use of the top bit of the rrclass field in the Question and