Another systemd-resolved problem in 17.04

[Chris Green]

On Thu, Jun 22, 2017 at 09:13:47AM -0400, Tom H wrote:
> On Thu, Jun 22, 2017 at 7:11 AM, Chris Green <cl at isbd.net> wrote:
> > On Thu, Jun 22, 2017 at 07:02:39PM +1000, Karl Auer wrote:
> >>
> >> It is barely possible that the nameserver is refusing to answer queries
> >> that arrive over IPv6 transport. If you control that nameserver you
> >> should certainly check its configuration. You could also see what
> >> happens when you query the same nameserver on its IPv4 address or (if
> >> it has one) its non-link-local address.
> >
> > So are you saying that the nameserver that's responding with REFUSE is
> > 'out there' on the internet somewhere?
> 
> It depends whether the "fe80..." address is you own (as I've assumed
> up to now) or not.
> 
Apparently it is:-

    root at t470:/var/log# ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
        link/ether c8:5b:76:de:2a:fc brd ff:ff:ff:ff:ff:ff
    3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 00:28:f8:3d:3b:aa brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.106/24 brd 192.168.1.255 scope global dynamic wlp4s0
           valid_lft 38680sec preferred_lft 38680sec
        inet6 fe80::56f5:f3cd:f369:bb34/64 scope link 
           valid_lft forever preferred_lft forever

-- 
Chris Green