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 gets used to blacklist ad/spam domains, and this behaviour would break that.
However, the more serious case is that if you have some *.example.com in /etc/hosts and then query the MX, SOA, or other non-address record for example.com then that query also fails. That's the part that I'll fix and Lennart agrees with. ** Summary changed: - systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another + resolved: correctly handle address families with /etc/hosts lookups -- 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: resolved: correctly handle address families with /etc/hosts lookups To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1644330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
