not sure when, probably after i change the wifi connections, lagrange is not able to resolve the domains. refresh of the page doesn't help, and that doesn't change for hours, the only way to bypass is to quit lagrange and start again.

i just did it again and that's why i don't remember what exactly was the error message. but i believe that was about resolving.

Posted in: s/Lagrange

🐙 norayr

Apr 09 · 6 weeks ago

3 Comments ↓

🕹️ skyjake [mod...] · Apr 10 at 07:17:

That's curious. Lagrange does nothing strange when it comes to DNS lookups, just basic `getaddrinfo` calls with no custom caching or other frills.

Maybe the OS has a per-process cache or something?

🐙 norayr [OP] · Apr 10 at 11:26:

interesting. i have no nscd or something. i'll try to attach to the process with strace and see what is happening next time it happens and write here.

🐙 norayr [OP] · Apr 10 at 11:27:

i think in happens both on my computer, which is gentoo, and on maemo, which is devuan.