These are chat archives for CZ-NIC/knot-resolver

20th
Feb 2019
Vladimír Čunát
@vcunat
Feb 20 06:23
Yes, kresc is rather buggy and experimental.
(Fortunately it's a completely separate process, so it seems unlikely to affect the daemon negatively.)
Georg
@teadur
Feb 20 12:12
what nameserver is used for root priming ?
Petr Špaček
@pspacek
Feb 20 12:12
It is randomly selected from root hints, which are compiled in.
I.e. one of IP addresses which was hosting the root zone at the time when we released that particular version.
(Assuming hints were not overriden in config.)
Georg
@teadur
Feb 20 12:14
[priming] cannot resolve any root adresses
points to them being overriden in config ?
Petr Špaček
@pspacek
Feb 20 12:15
It is most likely a communication error somewhere. I would suggest to enable verbose log and retry, it will spit huge amount of information.
You can add verbose(true) to your config and then capture log file.
Vladimír Čunát
@vcunat
Feb 20 12:16
Maybe you wanted docs: https://knot-resolver.readthedocs.io/en/stable/modules.html#c.hints.root_file (not sure I understood you)
Georg
@teadur
Feb 20 12:26
i have quite strange symptoms atm, i clear cach one domain resolves correctly
i can get like 3 queries then it servfails
clear cache again it works
disable cache it works
Petr Špaček
@pspacek
Feb 20 12:26
That's very weird. Please enable verbose log and post it here so we can have a look.
(And first of all, make sure you are running the latest version - 3.2.1.)
Georg
@teadur
Feb 20 12:30
now its working again as intended and the priming errors stopped aswell
both v4 and v6 are used for priming ?
seeing priming errors points to connectivity issues to where exactly ?
what resolves is used to resolve that addres
Petr Špaček
@pspacek
Feb 20 12:31
As I told you already, it might contact any of root servers - enable verbose log so we can see what exactly is going on.
Georg
@teadur
Feb 20 12:32
yep sorry the box gets more then my queries so its not trivial to read verbose log
Petr Špaček
@pspacek
Feb 20 12:32
(It might use IPv4 or IPv6, depending on configuration.)
Georg
@teadur
Feb 20 12:32
okey thanks i shall post verbose logs before asking stupid questions again :)
Petr Špaček
@pspacek
Feb 20 12:33
What you can do, to debug suspected connectivity issues, is to run another kresd instance (on different port and with separate cache directory) to see if the priming issue is reproducible or not.
Georg
@teadur
Feb 20 12:33
good idea thanks
edoo
@ookangzheng
Feb 20 13:11
One question. My server got 2 IPv6, inside kresd.conf, I listen to [::]:53, it doesnt work. I have to manually listen both of them. Is it normal?
Petr Špaček
@pspacek
Feb 20 13:23
It is not normal, it should work. If you are using systemd make sure you have the IP addresses listed in systemd socker configuration, see man kresd.systemd.
(Section Configuring network interfaces)