Ok, just to check, I changed /etc/resolv.conf to remove second
nameserver, added "domain .hm" and "search hm", added "fpc.hm"
to the respective entry in 10.2.2.3's /etc/hosts.
Result is, that localhost's systemd-resolved now no longer
knows about upstream dns 10.2.2.3 -- where else am I supposed
to configure that?
So, I re-added "nameserver 10.2.2.3" to /etc/resolv.conf, and
it really seems like it would once again take the second
nameserver-entry as that for upstream-dns.
Apparently, with "domain" and "search" in place, systemd-resolved
no longer makes any attempt to obtain information from routing
table, thus appears to work.
Nevertheless, apparently systemd-resolved DOES have a feature
where it queries local information about network devices to
get a list of ip-addresses whenever there is no domain/search
defined and a bare name queried. What is the reason behind
that feature, if the suggested solution to this ticket is just:
"don't use bare hostnames"?
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853669
Title:
systemd resolves own hostname to link local ipv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
