... by allowing .rdata to be a table.  Larger RRsets seem useful.

- use parser-detected $ORIGIN instead of looking at SOA owner
- skip records outside $ORIGIN (and warn) instead of nesting them
- simplify a bit, and tweak warnings

Also utilize table indexing.
This was a "regression" from extending RPZ support in 5.1.0.
NS and SOA are even mandatory, as RPZ is supposed to be a valid zone:
https://tools.ietf.org/html/draft-ietf-dnsop-dns-rpz-00#section-2

Merge branch '585-graphite-prevents-kresd-to-start-if-graphite-server-is-not-available' into 'master'

graphite: Reconnect to the graphite server when it was unavailable

Closes #585

See merge request !1014

It seems pointless to accumulate "late" connection attempts.

GC fixes

See merge request !1009

Vladimír Čunát authored 4 years ago and Tomas Krizek committed 4 years ago

I don't think it makes sense to ever package it separately from kresd,
so why should it have separate versioning? (could be confusing)

Vladimír Čunát authored 4 years ago and Tomas Krizek committed 4 years ago

On 32-bit systems the insufficient GC could commonly happen:
https://lists.nic.cz/pipermail/knot-resolver-users/2020/000265.html

The meaning of -f parameter got slightly changed, so that the buggy
computation could be greatly simplified.  GC seems to make sense when
most of cache space is used, in which case the difference is small.

Vladimír Čunát authored 4 years ago and Tomas Krizek committed 4 years ago

There were the usual effects: very incorrect timestamps (even by days),
and I suspect we could even lose some logs completely.

Fixes #582.

Trie relies on __attribute__(cleanup) and if its missing, it could
lead to memory leaks such as:

https://sonarcloud.io/project/issues?id=dns-oarc%3Adnsjit&issues=AXDyskhlrWLe1VCMvmVe&open=AXDyskhlrWLe1VCMvmVe

CI: optimize packaging tests

Closes #541

See merge request !947

Lukas Jezek authored 5 years ago and Tomas Krizek committed 4 years ago

and Ubuntu 18.04, Leap 15.2

daemon/tls: send fatal error on failed handshake

See merge request !1007

If the TLS handshake process fatally fails (e.g. no matching cipher
suite / cert), sent an alert to notify the peer.

modules/hints: NODATA answers also for non-address queries

See merge request !1005