Home
last modified time | relevance | path

Searched refs:nodata (Results 1 – 8 of 8) sorted by relevance

/freebsd/contrib/unbound/validator/
H A Dval_nsec3.h250 struct query_info* qinfo, struct key_entry_key* kkey, int* nodata,
H A Dval_nsec3.c1587 struct query_info* qinfo, struct key_entry_key* kkey, int* nodata, in nsec3_prove_nxornodata() argument
1592 *nodata = 0; in nsec3_prove_nxornodata()
1612 *nodata = 1; in nsec3_prove_nxornodata()
1614 *nodata = 1; in nsec3_prove_nxornodata()
H A Dvalidator.c1705 int nodata; in validate_cname_noanswer_response() local
1708 chase_reply->ns_numrrsets, qchase, kkey, &nodata, in validate_cname_noanswer_response()
1716 if(nodata) in validate_cname_noanswer_response()
/freebsd/contrib/unbound/services/
H A Drpz.c1865 goto nodata; in rpz_apply_clientip_localdata_action()
1878 nodata: in rpz_apply_clientip_localdata_action()
/freebsd/contrib/unbound/doc/
H A DChangelog1141 This turns completely empty responses, a type of noerror/nodata into
3711 - Fix auth-zone NSEC3 response for wildcard nodata answers,
3719 - Fix for auth zone nsec3 ent fix for wildcard nodata.
6294 - Fix #716: nodata proof with empty non-terminals and wildcards.
6997 - Add unbound-control flush_negative that flushed nxdomains, nodata,
7533 - fix bogus nodata cname chain not reported as bogus by validator,
7654 - Fix validation of nodata for DS query in NSEC zones, reported by
8220 - fix validation in this case: CNAME to nodata for co-hosted opt-in
8488 It could lead to a nodata reply getting into the cache if the search
8760 nxdomain and nodata distinguished.
[all …]
H A Drequirements.txt195 with attempt at no-DS proof) or a nodata answer with attempt
H A Dexample.conf.in868 # o static serves local data, else, nxdomain or nodata answer.
/freebsd/contrib/unbound/contrib/
H A Dfastrpz.patch436 + LIBRPZ_POLICY_NODATA =6, /* 'nodata': answer with ANCOUNT=0 */