Another systemd-resolved problem in 17.04

[Tom H]

On Thu, Jun 22, 2017 at 12:13 PM, Karl Auer <kauer at biplane.com.au> wrote:
> On Thu, 2017-06-22 at 11:18 -0400, Tom H wrote:
>> On Thu, Jun 22, 2017 at 10:06 AM, Karl Auer <kauer at biplane.com.au>
>> wrote:
>>> On Thu, 2017-06-22 at 09:13 -0400, Tom H wrote:
>>>>
>>>> It depends whether the "fe80..." address is your own (as I've
>>>> assumed up to now) or not.
>>>
>>> Link local addresses are by definition local to the link.
>>
>> Sure. But the fe80 of wlp4s0 is different from the one that resolved
>> is using...
>
> I don't understand your point. The responding link local address is, by
> definition, reachable on the local link. It is not "somewhere out
> there". It is possible that a link local address might leak and be used
> as a destination address on a link other than it's own, but it is not
> possible that a packet would reach such an address, or that it would
> respond. The link local address that responded with a REFUSED status is
> on his network, one way or another.

My point is/was that wlp4s0's ll address is
"fe80::56f5:f3cd:f369:bb34/64" whereas the upstream dns server that
resolved's using when it's failing is "fe80::1e74:dff:fe9d:5b1c%3" so
it's unclear to which computer this address belongs.

I know almost nothing about ipv6 (and that's even an exaggeration!)
but I seem to remember that an fe80 addresses that ends with a number
"...%3" is an MS address as opposed to a linux address that ends/can
end with an interface name.

To Chris: Is there an MS box with that fe80 address on the lan? Is
"192.168.1.2" an MS box? Is "fe80::1e74:dff:fe9d:5b1c%3" the
link-local address of the NIC that has "192.168.1.2" assigned?