On 2021-02-03 8:39 a.m., passiongnulinux@gmail.com wrote:
Hello the family ;)
It's me again, I have a person who told me about a dns cache problem, or something like that, in short, I have indeed since noticed that well after closing the Firefox browser, requests continue on the sites that I visited and that long after my last connection.
What about, bug or not? https://translate.google.fr/translate?hl=&sl=ru&tl=en&u=https%3A%2F%2Fwww.linux.org.ru%2Fforum%2Fgeneral%2F15622136&sandbox=1 the link speaks about it too.
DNS is a UDP protocol not a TCP protocol. Think of it this way. Your DNS mechanism asks for a resolution. What gets sent out amounts to a UDP shotgun blast. UDP is asynchronous. You don't know if a reply will come back to a specific request or when it will come back. Once sent, you can't cancel it. What you are getting amounts to a "long delayed echo" in radiophonics parlance. You send UDP requests to [A .. Z], get a reply from F and act on it. Meanwhile [A..T] might or might not reply and go into your cache. You finish and shut the application down. Then replies from [U..z} might or might not come in. Big Deal, that's the way it works. Its UDP after all. One the other hand, I have my firefox running day after day, so I never see this issue and even if I did i wouldn't see it as a problem, cost that's the way DNS works in a rich environment where there are many responders. You have to remember that DNS was designed some decades ago, in very sparse environment with unreliable connections and unreliable facilities. It solved the problems that existed then. The ones that exist now have to do with authenticity and integrity, not availability which are the problems that it faces now. -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg