[Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

>  you haven't told resolved about any upstream nameservers ...

As I said, my original  resolv.conf just had two nameserver entries, the
local one (127.0.0.53) and the upstream one.

>From that, all the diagnose-calls we did during this thread seemed to
show that systemd-resolved DID know the upstream DNS.  It really looks
like as if systemd-resolved looked for the configured nameservers,
recognized itself and took the other one as upstream.  See for example
comment #15: "DNS Servers: 10.2.2.3" in "Global" section.

Will look for where to create ticket for upstream systemd tomorrow. or
when I next have time for it...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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