> On 22 Jan 2023, at 09:54, Havard Eidnes wrote:
>
>> The consistency checks are not new. The message indicates that
>> the IXFR contained a delete request for a record that doesn't
>> exist or an add for a record that exists. Named recovers be
>> performing an AXFR of the zone.
>
> Interestin
> The consistency checks are not new. The message indicates that
> the IXFR contained a delete request for a record that doesn't
> exist or an add for a record that exists. Named recovers be
> performing an AXFR of the zone.
Interesting.
BIND 9.16.36 does not produce this log message, so it was e
The consistency checks are not new. The message indicates that the IXFR
contained a delete request for a record that doesn’t exist or an add for a
record that exists. Named recovers be performing an AXFR of the zone.
--
Mark Andrews
> On 22 Jan 2023, at 04:31, Havard Eidnes via bind-users
>
Hi,
I tried using BIND 9.18.10 as a downstream name server of an
OpenDNSSEC 2.1.8 installation, but after sorting out the ACL
issues on the OpenDNSSEC side, zone transfers failed with
messages such as these:
Jan 21 17:15:34 new-ns named[22056]: transfer of '4.38.158.in-addr.arpa/IN'
from 158.38.
In message , "Dav
enport, Steve M" writes:
> Can someone tell me the cause of the "not exact" error and how to troublesh=
> oot?
>
> 21-Mar-2011 11:01:24.931 xfer-in: error: transfer of '219.130.IN-ADDR.ARPA/=
> IN' from
> 130.219.31.5#53: failed w
Can someone tell me the cause of the "not exact" error and how to troubleshoot?
21-Mar-2011 11:01:24.931 xfer-in: error: transfer of '219.130.IN-ADDR.ARPA/IN'
from
130.219.31.5#53: failed while receiving responses: not exact
After this message appears, a retry on the tran
6 matches
Mail list logo
