[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-12-20 Thread Martin Pitt
See the summary from https://github.com/systemd/systemd/pull/4808: I can't convince Lennart about falling back to DNS for IPv6 if hosts has an IPv4 entry -- if hosts has some answer, it should be considered authoritative, and we should not mix different sources for the same query. Often /etc/hosts

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-12-07 Thread Martin Pitt
** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-16.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644330 Title: systemd-resolved assumes that /etc/hosts for one address family

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-12-02 Thread Martin Pitt
First PR sent upstream: https://github.com/systemd/systemd/pull/4808 ** Changed in: systemd (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644330

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-12-02 Thread Bug Watch Updater
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644330 Title: systemd-resolved assumes that /etc/hosts for one address family means it doesn't

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-12-02 Thread Martin Pitt
** Bug watch added: github.com/systemd/systemd/issues #4801 https://github.com/systemd/systemd/issues/4801 ** Also affects: systemd via https://github.com/systemd/systemd/issues/4801 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-12-02 Thread Martin Pitt
** Tags added: resolved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644330 Title: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another To

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-11-29 Thread Steve Langasek
I can confirm this behavior of 'getent ahosts'. 'getent ahostsv6' also shows :::207.[...] instead of the ipv6 address in this case. Nevertheless, the behavior is definitely different for e.g. 'ping6' or postfix address resolution depending on whether systemd-resolved is running. ** Changed

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-11-29 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644330 Title: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another To manage

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-11-29 Thread Martin Pitt
I cannot confirm that glibc's "dns" works like that -- it behaves the same as resolved: $ grep heise.de /etc/hosts 1.2.3.4 heise.de $ grep hosts /etc/nsswitch.conf hosts: files dns $ getent ahosts heise.de | grep STREAM 1.2.3.4 STREAM heise.de If I drop the heise.de entry

[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another

2016-11-29 Thread Martin Pitt
Confirmed. I wrote a test case for test/networkd-test.py which reproduces this. This should be committed together with the fix. ** Patch added: "test case" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1644330/+attachment/4784631/+files/1644330.patch ** Changed in: systemd (Ubuntu)