- Sep 21, 2017
-
-
-
Vladimír Čunát authored
We pushed all authority to the wire, but that was unnecessary, and in particular it clashed with not validating NS in authority when forwarding (new change). Let's only apply this to NSEC* RRs.
-
Vladimír Čunát authored
-
Vladimír Čunát authored
Sometimes I was getting huge RTT numbers in the output (>4G).
-
Vladimír Čunát authored
It's not very nice that this symbol used in hints.so is defined in sbin/kresd, but it touches the daemon structures and thus doesn't really belong into libkres.
-
Vladimír Čunát authored
"lua_" in name is not appropriate, as the function does no lua stuff anymore, so let's unify it to "engine_".
-
Vladimír Čunát authored
-
- Sep 20, 2017
-
-
Vladimír Čunát authored
Next time it will be directly visible what record fails to validate, which was the most time-expensive part when creating the parent commit.
-
- Sep 19, 2017
-
-
Vladimír Čunát authored
Fixes https://gitlab.labs.nic.cz/knot/knot-resolver/issues/248 Some (exotic?) resolvers add extra NS records but doesn't provide signatures for them even though we ask with +dnssec +cd. That lead to validation errors. Current example server: 198.101.242.72 Let's not try to validate them when FORWARDing, as we won't most likely need those records anyway (contrary to iteration mode).
-
Vladimír Čunát authored
-
- Sep 12, 2017
-
-
Vladimír Čunát authored
-
Vladimír Čunát authored
It's needed after the parent merge (sometimes, e.g. on macos). We always depended on it through libdnssec, so it's no real difference.
-
Vladimír Čunát authored
-
Vladimír Čunát authored
- move it to utils.c, so it's sensitive to later changes in verbosity - don't mark the lines with [tls], as they may come through libdnssec - use stdout like other verbose messages, instead of stderr (real errors)
-
- Sep 11, 2017
-
-
Vladimír Čunát authored
- expose the function as hints.root_file - use the same filename as Debian - remove the unneeded script - docs and some nitpicks
-
Petr Špaček authored
Limit maximal resolution time Closes #241 See merge request !368
-
Grigorii Demidov authored
-
- Sep 07, 2017
-
-
Vitezslav Kriz authored
-
Grigorii Demidov authored
-
Grigorii Demidov authored
-
Vladimír Čunát authored
-
Vladimír Čunát authored
Production kresd should compile with -DNDEBUG, so it wouldn't be affected by this, but it was annoying for debugging other problems. See https://gitlab.labs.nic.cz/knot/knot-resolver/issues/245
-
- Sep 06, 2017
-
-
Vladimír Čunát authored
-
-
- Sep 04, 2017
-
-
Vladimír Čunát authored
-
Vladimír Čunát authored
In particular, don't keep even a reset read-only transaction. This doesn't help with that MDB_BAD_TXN, but still it seems better.
-
Vladimír Čunát authored
The locking was done incorrectly - the copied text from man open(2) suggested creating a *unique* file and linking that one to the lockfile. Anyway, I don't think we need to support cache on NFSv3 on old kernels ;-)
-
Vladimír Čunát authored
-
Vladimír Čunát authored
-
Vladimír Čunát authored
-
Jiří Helebrant authored
Homepage link was broken – https://www.knot-resolver.cz/pages/try.html returns 404 (moved to /download during website redesign)
-
Vladimír Čunát authored
It's certainly a cleaner way.
-
- Sep 01, 2017
-
-
Vladimír Čunát authored
kresd never handled it. It's perhaps a rare occasion when different instances (attempt to) set different cache sizes.
-
Vladimír Čunát authored
-
Vladimír Čunát authored
Previously a read transaction could be held open by each fork indefinitely. That was done for better speed, but it had a downside of keeping old pages alive and potentially reading only old data, until some writes were attempted by that fork. Now kr_cache_ provides explicit API for suitable points where to break transactions, reusing the _sync command. On LMDB side the read-only transaction is only reset and later renewed, supposedly giving better performance than aborting (see LMDB docs on reset+renew). Performance: preliminary testing with two forks, resperf on comcast query-set shows no noticeable difference in peak QPS.
-
Vladimír Čunát authored
Fixes #150.
-
- Aug 31, 2017
-
-
Petr Špaček authored
Run unittests in CI under Valgrind memcheck See merge request !353
-
- Aug 30, 2017
-
-
Štěpán Kotek authored
New ci task has been added that checks for possible memory leaks when running unittests. Messages from valgrind are displayed only when leak is detected. refs #227
-
- Aug 29, 2017
-
-
Štěpán Kotek authored
-
Vitezslav Kriz authored
-