]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
projects / thirdparty / knot-resolver.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 95a393d) | patch
FORWARD: don't validate NS in authority section
authorVladimír Čunát <vladimir.cunat@nic.cz>
Tue, 19 Sep 2017 13:43:03 +0000 (15:43 +0200)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Tue, 19 Sep 2017 14:36:12 +0000 (16:36 +0200)
commitfea13fcf4cdbdebd0af75dd2afc3098a73f6d9b9
treec4d15109e346686c250bd118ee6375545ffc07c7tree
parent95a393d115ff3bd52cfb3a5480f1de16d07860fecommit | diff
FORWARD: don't validate NS in authority section

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).
NEWS diff | blob | blame | history
lib/layer/iterate.c diff | blob | blame | history
Mirror of https://gitlab.nic.cz/knot/knot-resolver.git