Another systemd-resolved problem in 17.04

[Karl Auer]

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.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A
Old fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B