> 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?
If you use systemd-networkd to configure your network (or, netplan,
which will indirectly configure networkd or network-manager for you),
then systemd-resolved will be updated to know what your actual upstream
nameserver(s) are; you can query what current upstream nameservers
resolved is using with the 'systemd-resolve --status' command.
If you use ifupdown, there is a dhclient hook that tells resolved (or
resolvconf) about your upstream nameservers.
If you manually configure your network, it's up to you to also manually
configure your /etc/resolv.conf file, or manually tell resolved about
your upstream nameservers, which you can do with the systemd-resolved
command (see its man page).
> It consults the routing table, and, when doing so, it deals wrongly with
> link-local
> inet6 addresses. That's what this bugreport was about.
Why is it wrong? All the ipv6 addresses it resolves for its own
hostname are reachable locally.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
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
