3 ms·
Because the basic glibc resolver is still in the last century. (No cache, no DNSSEC, no link-local multicast name resolution, no concept of per-interface DNS re
by pas 9y ago
Because the basic glibc resolver is still in the last century. (No cache, no DNSSEC, no link-local multicast name resolution, no concept of per-interface DNS resolution worlds, and so on. See the relevant part of the NEWS file: https://github.com/systemd/systemd/blob/master/NEWS#L3966 https://github.com/systemd/systemd/blob/master/NEWS#L3966 )
See also:
https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html# https://www.freedesktop.org/software/systemd/man/systemd-res...
- agwa 9y agoCache and DNSSEC do not require a non-standard DBUS API. LLMNR and per-interface DNS resolution are features that very few applications need. Those that do can link with their own resolver libraries.
- JdeBP 9y agonscd, which is part of the GNU C library, is a cache. Moreover: Strictly speaking what is in the C library, to use the jargon, is a stub resolver; with all of the things that you mention not actually belonging in the C library in the first place.
- pas 9y agoYes, you're of course right. And Ubuntu used dnsmasq as a caching resolver for quite a long time. (Via using 127.0.0.1 in /etc/resolv.conf) systemd-resolved is sort of the same thing (and it listens on 127.0.0.53, which doesn't require the DBus dance that the nss plugin does) I don't know why systemd reinvented the wheel (nscd), but probably because nscd lacks a DBus API.