Home
last modified time | relevance | path

Searched refs:NSEC (Results 1 – 12 of 12) sorted by relevance

/src/usr.bin/mkuzip/
H A Dmkuz_time.h31 #define NSEC(x) ((x)->tv_nsec) macro
34 (double)NSEC(s) / 1000000000.0)
/src/contrib/unbound/doc/
H A DTODO3 o NSEC/NSEC3 aggressive negative caching, so that updates to NSEC/NSEC3
49 * aggressive negative caching for NSEC, NSEC3.
H A Drequirements.txt188 maybe NSEC or NSEC3 records present.
201 check NSEC/NSEC3.
259 If the domain is DNSSEC signed, by the way, then NSEC records are
260 updated more carefully. If one of the NSEC records in an NXDOMAIN is
266 This speeds up building chains of trust, and uses NSEC and NSEC3
268 the bare NSEC(3) information is sufficient, probably picked up from
272 NSEC and NSEC3 records were obtained) if available otherwise network
H A DFEATURES99 4033-4035: DS, RRSIG, NSEC, DNSKEY
H A DChangelog566 - Fix to limit NSEC TTL for messages from cachedb. Fix to limit the
623 - Fix to limit NSEC and NSEC3 TTL when aggressive nsec is
2769 - Fix #441: Minimal NSEC range not accepted for top level domains.
5076 - Fix memory leak when caching wildcard records for aggressive NSEC use
5175 - Do not use cached NSEC records to generate negative answers for
5247 aggressive NSEC.
5270 - Aggressive NSEC tests
5280 - Added tests with wildcard expanded NSEC records (CVE-2017-15105 test)
5281 - Processed aggressive NSEC code review remarks Wouter
5284 - Aggressive use of NSEC implementation. Use cached NSEC records to
[all …]
H A Dunbound-control.rst1325 The number of queries answered using cached NSEC records with NODATA RCODE.
1331 The number of queries answered using cached NSEC records with NXDOMAIN
H A Dexample.conf.in589 # Aggressive NSEC uses the DNSSEC NSEC chain to synthesize NXDOMAIN
H A Dunbound.conf.rst1903 Aggressive NSEC uses the DNSSEC NSEC chain to synthesize NXDOMAIN and other
/src/tools/regression/sockets/udp_pingpong/
H A Dudp_pingpong.c102 #define NSEC(x) ((x)->tv_nsec) macro
109 NSEC(ts) = (tv)->tv_usec * NSEC_IN_USEC; \
/src/contrib/ldns/
H A DChangelog55 * Set NSEC(3) ttls to the minimum of the MINIMUM field of the SOA
254 * bugfix #661: Fail NSEC3 signing when NSEC domainname length
432 * bugfix #398: Allow NSEC RRSIGs before the NSEC3 in ldns-verify-zone
506 * Fix creating NSEC(3) bitmaps: make array size 65536,
522 NSEC with many types and max parse length in hosts_frm_fp routine
585 * Fix NSEC record after DNSKEY at zone apex not properly signed.
644 * Bugfix: NSEC3 bitmap contained NSEC
657 * Fix occasional NSEC bitmap bogus
813 * TTLS are now correctly set in NSEC(3) records when signing zones
832 rbtree and links signatures and NSEC(3) records directly to their
[all …]
/src/contrib/unbound/contrib/
H A Daaaa-filter-iterator.patch17 Aggressive NSEC uses the DNSSEC NSEC chain to synthesize NXDOMAIN and other
H A Dfastrpz.patch3481 /* NSEC proof did not work, try next */
3504 /* Apparently, no available NSEC/NSEC3 proved NODATA, so