Re: "not exact" error message

2023-01-22 Thread Mark Andrews
> 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

Re: "not exact" error message

2023-01-21 Thread Havard Eidnes via bind-users
> 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

Re: "not exact" error message

2023-01-21 Thread Mark Andrews
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 >

"not exact" error message

2023-01-21 Thread 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.