Another systemd-resolved problem in 17.04

[Chris Green]

On Thu, Jun 22, 2017 at 07:02:39PM +1000, Karl Auer wrote:
> On Thu, 2017-06-22 at 08:55 +0100, Chris Green wrote:
> > On Thu, Jun 22, 2017 at 08:41:16AM +1000, Karl Auer wrote:
> > > If the nameserver is listening, but refusing to serve you, you'll
> > > get a response with a REFUSED status. Don't use "+short" or you
> > > won't see it:
> > 
> > Yes, exactly what I get:-
> > 
> >     ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 7839
> 
> Well, in a way that's good. You now know that your network is fine,
> that your queries are reaching the nameserver, and that for some reason
> the nameserver is returning "REFUSED". You have taken your local
> caching nameserver out of the equation.
> 
> Progress! :-)
> 
> 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?  If so I'm surprised as I have
IPV6 support turned off in my router so I don't understand how IPV6
packets can be sent and received at all.

-- 
Chris Green