Lines Matching refs:rrset
220 /** allocate and initialize an rrset structure; this function is based
226 struct ub_packed_rrset_key* rrset = regional_alloc_zero(
227 region, sizeof(*rrset));
228 if(!rrset) {
232 rrset->entry.key = rrset;
240 rrset->entry.data = pd;
241 rrset->rk.dname = regional_alloc_zero(region, 1);
242 if(!rrset->rk.dname) {
246 rrset->rk.dname_len = 1;
247 rrset->rk.type = htons(rrtype);
248 rrset->rk.rrset_class = htons(rrclass);
249 return rrset;
469 * a lower-level module and it might not build the rrset to meet the
470 * assumption. In fact, an rrset specified as response-ip-data or generated
473 * function ensures the copied rrset data are in a contiguous region so
476 * - It doesn't copy RRSIGs (if any) in 'key'. The rrset will be used in
483 * This function returns the copied rrset key on success, and NULL on memory
676 * See if response-ip or tag data should override the original answer rrset
687 * @param rrset_id: the rrset ID in 'rep' to which the action should apply
716 /* Extract parameters of the original answer rrset that can be
719 * rrset is a CNAME target.*/
741 /* If we are using response-ip-data, we need to make a copy of rrset
742 * to replace the rrset's dname. Note that, unlike local data, we
753 /* Build a new reply with redirect rrset. We keep any preceding CNAMEs
754 * and replace the address rrset that triggers the action. If it's
835 const struct ub_packed_rrset_key* ATTR_UNUSED(rrset),
1035 * CNAME, record the CNAME rrset so the caller can take
1316 qname = local_alias->rrset->rk.dname;