On 18 Jun 2015 3:51 am, "Lennart Poettering" <<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>> wrote: > > On Wed, 17.06.15 19:48, Igor Bukanov (<a href="mailto:igor@mir2.org">igor@mir2.org</a>) wrote: > > > On 17 June 2015 at 15:27, Lennart Poettering <<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>> wrote: > > > To hook up local name service > > > clients people should use the "nss-resolve" NSS module, which ensures > > > that gethostbyname() and friends use resolved as backend. > > > > I suppose then non-glibc clients should deal with that on its own. I > > thought converting LLMNR into DNS would be a reasonable hack, but then > > if the translation requires too much insanity, then indeed it is > > better not to do that. > > If people use libraries to do DNS manually, then they'll do *DNS* > manually, and we shouldn't interfere with that really. > > Usually people pick non-libc DNS libraries because they need async > behaviour. I am pretty sure that's a pretty bad reason though and if > you want async behaviour you should use sd-resolve or so. I've also used them because I - need other record types (e.g. SRV) - want to use DNSSEC - Want to choose between recursive and stub resolvers FWIW, I use <a href="http://25thandclement.com/~william/projects/dns.c.html">http://25thandclement.com/~william/projects/dns.c.html</a> in many projects. It parses nsswitch.conf, but only cares about a few predetermined values. Maybe it should gain some features in this area?