zlacker

[return to "Understanding DNS Resolution on Linux and Kubernetes"]
1. zokier+xB7[view] [source] 2025-03-26 11:39:39
>>fanf2+(OP)
It's bit curious that traditionally UNIX systems did not run local DNS resolver daemons and instead the resolv.conf (and nsswitch.conf) persisted for so long. In addition to potentially simplifying configuration, having a daemon would allow system-wide dns caching, something I'd imagine would have been especially valuable back in the days of slow networks. Unix has daemons for everything else so that's why it feels odd that name resolution got baked into libc
◧◩
2. teknop+Y48[view] [source] 2025-03-26 14:53:06
>>zokier+xB7
I don't see why system wide dns caching would be of use?

How many different programs in the same process space hit so many common external services individual caching of names is not sufficient?

Article lists a bunch of fun with systemd running junk in containers that seem counterproductive to me. A lot of systemd stuff seems to be stuff useful on a laptop that ends up where it's really not wanted.

Local dns caching seems like a solution looking for a problem to me. I disable it whereever I can. I have local(ish) dns caches on the network. But not inside lxc containers or Linux hosts.

[go to top]