Searched refs:chase_reply (Results 1 – 2 of 2) sorted by relevance
642 for(i=chase_reply->an_numrrsets; i<chase_reply->an_numrrsets+ in validate_msg_signatures()666 for(i=chase_reply->an_numrrsets+chase_reply->ns_numrrsets; in validate_msg_signatures()819 for(i=chase_reply->an_numrrsets; i<chase_reply->an_numrrsets+ in validate_positive_response()846 chase_reply->rrsets+chase_reply->an_numrrsets, in validate_positive_response()907 for(i=chase_reply->an_numrrsets; i<chase_reply->an_numrrsets+ in validate_nodata_response()946 chase_reply->rrsets+chase_reply->an_numrrsets, in validate_nodata_response()999 for(i=chase_reply->an_numrrsets; i<chase_reply->an_numrrsets+ in validate_nameerror_response()1031 chase_reply->rrsets, chase_reply->an_numrrsets+ in validate_nameerror_response()1193 chase_reply->an_numrrsets+chase_reply->ns_numrrsets, in validate_any_response()1309 chase_reply->rrsets+chase_reply->an_numrrsets, in validate_cname_response()[all …]
175 struct reply_info* chase_reply; member