Hi there,
On Tue, 17 Nov 2020, Boylan, Ross wrote:
I have been experiencing NXDOMAIN errors ...
... There are a lot of complications.
... The remote machine is only accessible though VPN
... the nameserver ... is also accessible only through VPN
... The VPN connection has always been a bit to
On 17.11.20 05:41, Boylan, Ross wrote:
One other detail may be important: I just added a bridge interface and
virtual machines. I presume the VPN tunnel was using the hardware
interface (enp5s0) before, and is using the bridge (br0) now. OpenConnect
creates the tunnel (tun0); both the name and
On 16.11.20 22:58, Boylan, Ross wrote:
I have been experiencing NXDOMAIN errors persistently, though not 100% of
the time, for a machine I am trying to reach. The queries worked OK
before today. I not only don't know what's causing it, but am having
trouble tracing what's going on inside of bin
Ross,
I don’t have an answer for you what’s happening, but it would help you with the
debugging if you see what happens on the wire? Using wireshark is usually
helpful.
Also reviewing named.conf after you made the networking change might help and
sharing the anonymized named.conf might trigger
One other detail may be important: I just added a bridge interface and virtual
machines. I presume the VPN tunnel was using the hardware interface (enp5s0)
before, and is using the bridge (br0) now. OpenConnect creates the tunnel
(tun0); both the name and inspection of the code indicate the tu
5 matches
Mail list logo
