Le vendredi 05 février 2021 à 19:28 +0000, Brendan McKenna a écrit :
Hi,
What's happening is that nscd (the Name Service Caching Daemon) is updating its cache entries. When you visit a web site, it makes a DNS request to look up the site. The response has a time-to-live value associated with it. When that exipres, nscd re-issues the request to update its cache, on the assumption that you will (eventually) make the same request again at some point in the future.
So, if you want to eliminate the repeated requests, just shut nscd down and/or don't start it in the future. That way, the only time(s) you will see DNS requests being made is when you are actually browsing to a site, and not later.
Even with nscd running, it will (eventually) stop refreshing the cache entries -- the size of the cache is finite, so if you make enough DNS requests, eventually the "older" ones will be removed from the cache to make room for information pertaining to more recently-requested information.
Brendan
On 05/02/2021 18:32, passiongnulinux@gmail.com wrote:
I will open a request on bugzilla by giving the link of this discussion.
Thank you very much for your help.
Le vendredi 05 février 2021 à 19:21 +0100, Per Jessen a écrit :
passiongnulinux@gmail.com wrote:
Good evening,
Thank you for continuing to understand, on my side I'm quite lost and I ask if it's suddenly a bug or a function? Should we make a bug report on our bugzilla or not?
If you believe the situation is a problem or a security issue, a bug report is a good idea.
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.