Lines Matching refs:rrset

226 /** allocate and initialize an rrset structure; this function is based
232 	struct ub_packed_rrset_key* rrset = regional_alloc_zero(
233 		region, sizeof(*rrset));
234 	if(!rrset) {
238 	rrset->entry.key = rrset;
246 	rrset->entry.data = pd;
247 	rrset->rk.dname = regional_alloc_zero(region, 1);
248 	if(!rrset->rk.dname) {
252 	rrset->rk.dname_len = 1;
253 	rrset->rk.type = htons(rrtype);
254 	rrset->rk.rrset_class = htons(rrclass);
255 	return rrset;
477  *   a lower-level module and it might not build the rrset to meet the
478  *   assumption.  In fact, an rrset specified as response-ip-data or generated
481  *   function ensures the copied rrset data are in a contiguous region so
484  * - It doesn't copy RRSIGs (if any) in 'key'.  The rrset will be used in
491  * This function returns the copied rrset key on success, and NULL on memory
649  * See if response-ip or tag data should override the original answer rrset
660  * @param rrset_id: the rrset ID in 'rep' to which the action should apply
689 		/* Extract parameters of the original answer rrset that can be
692 		 * rrset is a CNAME target.*/
714 	/* If we are using response-ip-data, we need to make a copy of rrset
715 	 * to replace the rrset's dname.  Note that, unlike local data, we
726 	/* Build a new reply with redirect rrset.  We keep any preceding CNAMEs
727 	 * and replace the address rrset that triggers the action.  If it's
807 	const struct ub_packed_rrset_key* ATTR_UNUSED(rrset),
1039 		 * CNAME, record the CNAME rrset so the caller can take
1324 		qname = local_alias->rrset->rk.dname;