When resolving just NS names and addresses which won't go to answers,
our cache can satisfy them with just parent-side records.
Now we also make iterator consistent with that, and it will cut short
if a delegation satisfies what the kr_query wants.

There's a general risk that we will never get the child-side records,
and in practice the parent-side ones are sometimes "less accurate".
This change may increase this risk (to NS addresses in particular),
but we'd better consider addressing the risk later and systematically.
A suggestion is to refresh the records asynchronously:
https://tools.ietf.org/html/draft-ietf-dnsop-ns-revalidation

---
State before this commit lead to a weird behaviour where some IPv4-only
tests in Deckard (namely `iter_pcdiff.rpl`) were failing with IPv6
turned off.

This was due to the resolvers' internal preference towards AAAA records
for NS names.  With IPv6 networking on, NS name resolution was first
done for AAAA record and the glue (containing A record for the NS name
in question) from parent zone was put into cache.  As the AAAA
resolution failed (there is no AAAA for this NS name), A was queried
next and was satisfied from cache.

With IPv6 off, there is no query for the AAAA record, so no A record
from glue gets put in to the cache.  A record is resolved first, and
resolution ignores the glue in parent zone and continue to the child
zone which might be broken (intentionally in the case of that
`iter_pcdiff.rpl` test).

view tweaks

See merge request !1112

It's more consistent with what we do.  Now it will look like:
[system] error while loading config: .../lib/knot-resolver/kres_modules/view.lua:28: failed to parse subnet [::1]/128 (workdir '/foo/bar')

inet_pton() has slightly unexpected return values.
Only one function was wrong; I don't count the unused kr_straddr_join().

:func: directive automatically always adds brackets. This results in
links such as "policy.PASS()", which can be confusing, since the actual
policy is supposed to be "policy.PASS".

Using :any: results in links without the added brackets, which makes
non-function policies less confusing.

Transform Graphite tags into Prometheus labels

Closes #650

See merge request !1109

release 5.2.1

See merge request !1108

Renumber module fix

See merge request !1107

Petr Špaček authored 4 years ago and Tomas Krizek committed 4 years ago

Finally it does not rely on ordering in the answer.
Stringification seemed like an easy hack for tests, let's see how it
works in the long term.

contrib/cleanup: loosen type-checking in auto_free

See merge request !1100

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

- advantage:    `auto_free anyType *foo;` works (for anyType != char)
- disadvantage: `auto_free anyType bar;` is also accepted,
  though I expect such problems will be relatively easy to debug.

ci: improve GH actions error handling

See merge request !1106

doh2: restricts endpoints to doh and dns-query

Closes #636

See merge request !1104

In English, the final letter is doubled when a word of two or more
syllables has stress on the final syllable so a correct form is
"occurred".

The difference is on "negative" char values, in which case
the prints were way too long.

doh2: send cache-control header

Closes #617

See merge request !1095

ci: move macOS build to GitHub Actions

See merge request !1099

Tomas Krizek authored 4 years ago and Petr Špaček committed 4 years ago

https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing