Hi Warren,
> This sounds very much like a path MTU issue -- it starts the transfer,
> gets part of the way and then a big packet doesn't make it through...
> Are you doing the test dig from the same machine? And if so, from the same IP?
Yes, I test from the same system using the same source addre
Hi usually it is a common problem. If u'r succesful via u'r root access, it
mean is not a network or BIND related but FULL PATH and File Permission issue.
Daemons does not run with root privilege for priviledge escalation and
specially bind and others are jailed.
Check if all paths are not rela
On Mon, Feb 10, 2020 at 12:53 PM von Dein, Thomas
wrote:
>
> Hi everyone,
>
> we are unable to complete root zone transfer from our nameservers. This is
> the error we're getting:
>
> Feb 10 18:33:32 bedns2 named[61444]: transfer of './IN' from 192.0.47.132#53:
> connected using 192.168.1.1#1128
Hi everyone,
we are unable to complete root zone transfer from our nameservers. This is the
error we're getting:
Feb 10 18:33:32 bedns2 named[61444]: transfer of './IN' from 192.0.47.132#53:
connected using 192.168.1.1#11281
Feb 10 18:33:33 bedns2 named[61444]: transfer of './IN' from 192.0.47.
4 matches
Mail list logo