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. znpy+AO7[view] [source] 2025-03-26 13:11:39
>>zokier+xB7
> traditionally

because in the tradition there was a (forwarding) dns server somewhere in the local network to do caching for everybody.

nowadays most decent linux distributions have a very good caching dns resolver (systemd-resolved) so that's not an issue anymore.

[go to top]