On Thu, 18.06.15 07:57, Daurnimator (q...@daurnimator.com) wrote:
On 18 Jun 2015 3:51 am, Lennart Poettering lenn...@poettering.net wrote:
On Wed, 17.06.15 19:48, Igor Bukanov (i...@mir2.org) wrote:
On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net
wrote:
To hook
On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net 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
On Wed, 17.06.15 19:48, Igor Bukanov (i...@mir2.org) wrote:
On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net 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.
On 18 Jun 2015 3:51 am, Lennart Poettering lenn...@poettering.net wrote:
On Wed, 17.06.15 19:48, Igor Bukanov (i...@mir2.org) wrote:
On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net
wrote:
To hook up local name service
clients people should use the nss-resolve NSS
Hello,
perhaps I missed something, but it seems that systemd-resolved cannot
be configured to serve the same role as dnsmasq and be a DNS server
for local machine. I.e. I cannot just have nameserver 127.0.0.1 in
/ertc/resolv.conf and get LLMNR resolution working for progams that
only use
On Wed, 17.06.15 15:19, Igor Bukanov (i...@mir2.org) wrote:
Hello,
perhaps I missed something, but it seems that systemd-resolved cannot
be configured to serve the same role as dnsmasq and be a DNS server
for local machine. I.e. I cannot just have nameserver 127.0.0.1 in
/ertc/resolv.conf
