In data sabato 6 febbraio 2021 20:18:13 CET, Carlos E.R. ha scritto:
On 06/02/2021 17.55, passiongnulinux@gmail.com wrote:
Le vendredi 05 février 2021 à 19:28 +0000, Brendan McKenna a écrit :
Hi,
Hello,
Please try to explain, it's already clearer, so it's not a bug but a function.
No bugzilla.
I told you yesterday, that the comments at the end of that link say that the /culprit/ was *nscd*. It is a "feature", that is how it works.
ok so i'm not doing anything, thanks.
It is simple.
The people on the link you posted:
<https://translate.google.fr/translate?hl=&sl=ru&tl=en&u=https%3A%2F%2Fwww.l inux.org.ru%2Fforum%2Fgeneral%2F15622136&sandbox=1>
clearly say that the symptoms stop when stopping nscd service.
The manual page explains what it is:
nscd - name service cache daemon
And it does its job. There is a configured time during which it will store that name to address conversion, which means it has to query upstream when upstream says it is time out. It is doing its job.
If you don't like it, you can stop it permanently, but then internet (and other things) will be slower. Your choice.
Is nscd actually useful at all if he would use a caching server like unbound or dnsmasq? My understanding is that it would be only the case if he is using normal resolf.conf, am I mistaken? So he could in this case use a workaround to install / use such setup and stop nscd. Maybe not correct, please educate me if I am mistaken. Thanks.