On 2022-04-20 01:03:36 +0300, Michael Tokarev wrote: > 20.04.2022 00:58, Vincent Lefevre wrote: > > On 2022-04-20 00:43:48 +0300, Michael Tokarev wrote: > > > 20.04.2022 00:40, Vincent Lefevre wrote: > > > > > > > > Well, systemd already have its own nameserver configuration and its > > > > > own resolver cache which does not need any reload of daemons, since > > > > > resolv.conf does not change (It does not change with resolvconf and > > > > > unbound running with resolvconf hook enabled, either, and postfix > > > > > already needs no restart). > > > > > > > > But AFAIK, it doesn't have a way to fall back to the nameservers > > > > provided by DHCP. > > > > > > Yes. Neither does unbound or other nameservers shipped in Debian, > > > because there's just no _notion_ of "fall back". > > > > Wrong. The normal use of /etc/resolv.conf via glibc does > > (so, assuming that resolvconf is not installed). > > See additional information in my mail to bug 1003135. > > glibc is not a nameserver, Vincent. Please actually read what I write > before saying I'm wrong.
glibc is not a nameserver, but it provides functions to resolve hostnames. This is what applications see. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
