Home | History | Annotate | Download | only in mDNSCore

Lines Matching refs:RRSet

990 		const AuthRecord *s1 = rr->RRSet ? rr->RRSet : rr;
991 const AuthRecord *s2 = (*rp)->RRSet ? (*rp)->RRSet : *rp;
1125 // rr->RRSet = set to mDNSNULL in mDNS_SetupResourceRecord; may be overridden by client
2173 // the whole RRSet as an atomic unit. That means that if we have any other records with the same name/type/class
2175 // record, then other RRSet members that have not been sent recently will get flushed out of client caches.
2181 if (rr->ImmedAnswer) // If we're sending this as answer, see that its whole RRSet is similarly marked
2189 else if (rr->ImmedAdditional) // If we're sending this as additional, see that its whole RRSet is similarly marked
2318 // make sure we haven't already sent any other members of its RRSet -- if we have, then they
5542 // Find the canonical RRSet pointer for this RR received in a packet.
5543 // If we find any identical AuthRecord in our authoritative list, then follow its RRSet
5553 while (rr->RRSet && rr != rr->RRSet) rr = rr->RRSet;
5568 // are members of the same RRSet, then this is not a conflict.
5579 const AuthRecord *ourset = our->RRSet ? our->RRSet : our;
6508 // delivering some records of the RRSet first and then the remainder a couple of milliseconds later was causing
6512 // abort our TCP connection, and not complete the operation, and end up with an incomplete RRSet in our cache.
6513 // Next time there's a query for this RRSet we'll see answers in our cache, and assume we have the whole RRSet already,
6515 // Accordingly, if we get a uDNS reply with kDNSFlag0_TC set, we bail out and wait for the TCP response containing the entire RRSet.
6523 // answer as being the authoritative complete RRSet, and respond by deleting all other
6952 // bit set, and either (a) if they're fresh, just make sure the whole RRSet has the same TTL
6958 // "fresh" and would be incorrectly resurrected back to the same TTL as the rest of the RRSet,
6971 // If record is recent, just ensure the whole RRSet has the same TTL (as required by DNS semantics)
6975 // If we find mismatched TTLs in an RRSet, correct them.
9215 set->RR_A.RRSet = &primary->RR_A; // May refer to self
9245 if (intf->RR_A.RRSet == &set->RR_A)
9246 intf->RR_A.RRSet = A;