GitLab

                        an assertion failure.

to be used for debugging

                        signed query could crash the server.

                        block were not correctly reference counted, causing
                        a memory leak.

like both the global and per-zone counterparts now do

                        as expected.

cache if validation fails.

unless the query has the cd bit set.

Don't #define mins/maxes if they are already defined. (per MG)

			'glue-from-cache' now supported in view and global
			options statement.

key (which should be the case anyway, but it never hurts to check).  Also
fix a memory leak and change a few _tostruct() calls to not allocate memory.

insecurity proof also failed, the validator event should normally contain
the error from the positive validation.

when adding the deletion rdataset so that rdatasets can be deleted
regardless of their trust level

query still doesn't completely work, since the resolver needs to be modified
also.  Basically, if data is in the cache and trust == pending, it will now
be returned when the cd bit is set.

but this is no longer the case.  Thus, the DNS_DBADD_FORCE option did not take effect
if the existing data was at level dns_trust_ultimate.  Since the DNS_DBADD_FORCE
option is currently used only with cached data, no actual harm has been done.

                        options in dig.

argument.

was not initialized

the yea_and_nay and notify_setting grammar rules