I was wondering if you could shed some light on DNS caching, and why the BOINC client apparently keeps records for days, which would seem to ignore the TTLs associated with the records? (the recent DNS changes for Leiden would indicate this; requiring a client restart)
Actually libCurl handles all the DNS stuff. We just pass the server name to libCurl and it handles all the OS details. I took a quick peek at the libCurl source and it looks like they have an internal DNS cache. It also appears that they have a way to expire the DNS cache entries. It isn’t clear to me at the moment if we are supposed to call an API to expire DNS cache entries or if that is handled automatically as part of the easy API set.
I’ll look into it a bit more to see if I can figure it out.
To submit questions for next week just click on the comments link below and submit your question.
Thanks in advance.
—– Rom
This post was last modified on December 13, 2020 12:26 pm
2020 turns out to be a hardware refresh year for ROMWNET. I've upgraded the network…
After a bit of research and experimentation, I figured out how to fix my permalink…
After a seriously long time, I've finally upgraded my blogging platform to WordPress. Dasblog was…
Original post: New BOINC Manager Design Project: BOINC Sentinels Some time back, I started BOINC…
So I have been working on a little side project on and off for a…
Well I believe I have found and fixed the screen saver issue that has been…
This website uses cookies.