GitLab

                        key as per RFC 7344, Section 4.1. [RT #37215]

                        a NSEC3 chain incrementally. [RT #23702]

                        before marking it as insecure.  One set of conditions
                        that can trigger this occurs naturally when rolling
                        DNSKEY algorithms.  [RT #22309]

                        in a optout, delegation only zone with no secure
                        delegations. [RT #22007]

                        current NSEC3PARAM record in use for zone named
                        could dereference a uninitialised pointer attempting
                        to obtain a lock. [RT# 21868]

                        validation.  default dnssec-validation no; to
                        be changed to yes in 9.5.0.  [RT #15674]

                        which contained CNAMES. [RT# 11237]

enable-dnssec -> dnssec-enable

                        running tests. [RT #9091]

                        DNSSEC specify "enable-dnssec yes;" in named.conf.

files, so that tests succeed while transfer-source is still being (ab)used as
the notify source address

own CVS tree will help minimize CVS conflicts.  Maybe not.
Blame Graff for getting me to trim all trailing whitespace.

sockets and causing failures on some platforms

Fix out output

- Added an insecure child of a secure parent (insecure.secure.example)
- Added a privately secure child of a secure parent (private.secure.example)