> 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20<link>" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp