The CNAMEs used as examples in the documentation imply that they are
fully-qualified, so they should end with a dot.

The values that can be used for the `geodb-keys` configuration item
depend on the database being used. Point that out and provide a hint on
how to find which keys are available in a database.

bi-nodes: fix double free by double unify on FULL update

See merge request !1016

Conrad Hoffmann authored 5 years ago and Daniel Salzman committed 5 years ago

Weighted records are a useful mechanism for situations where uneven
load-balancing is required, such as a canary environment or a gradual
roll-out.

Instead of using deterministic properties like location or source IP,
allow to attach a statistical weight to a certain record. The ratio of
a record's weight to the sum of the weights of all records for a domain
determines the record's likelyhood to be the result of a random pick.

fixes #646

Blocking zone event triggers

See merge request !1015

adjust: refactored measurement of zone size and max TTL

See merge request !1014

kjournalprint: fix changeset history depth limitation

See merge request !1013

nsec/nsec3: refactor of incremental updates

See merge request !1012

Libor Peltan authored 5 years ago and Daniel Salzman committed 5 years ago

now it shall less depend on the whole zone size

Knotc semcheck warning

Closes #643

See merge request !1011

optimization: adjusting: mesure zone size incrementally for updates

See merge request !1005

offline ksk: don't touch error.code if set to error value

See merge request !1009

dnssec: bugfix: correct computing with infinite key lifetime

See merge request !1008

nsec3: allow infinite validity of nsec3salt

See merge request !1007

Additionals reverse tree

See merge request !1004