Re: "can't validate existing negative responses (not a zone cut)" messages

2010-12-06 Thread Mark Andrews
In message , Chris Tho mpson writes: > On Oct 3 2010, I wrote: > > >Since upgrading our main recursive nameservers to BIND 9.7.2-P2 (and > >using a trust anchor for the root and lookaside via dlv.isc.org) I am > >seeing a scatter of warning messages like this: > > > >Oct 1 19:47:19 dnssec: warni

Re: "can't validate existing negative responses (not a zone cut)" messages

2010-12-06 Thread Chris Thompson
On Oct 3 2010, I wrote: Since upgrading our main recursive nameservers to BIND 9.7.2-P2 (and using a trust anchor for the root and lookaside via dlv.isc.org) I am seeing a scatter of warning messages like this: Oct 1 19:47:19 dnssec: warning: validating @1c29d580: 115.197.101.95.IN-ADDR.ARPA

Re: "can't validate existing negative responses (not a zone cut)" messages

2010-10-24 Thread Chris Thompson
On Oct 22 2010, Tony Finch wrote: On Sun, 3 Oct 2010, Chris Thompson wrote: Oct 3 16:53:10 dnssec: warning: validating @14c9cd70: 98.206.101.95.IN-ADDR.ARPA PTR: can't validate existing negative responses (not a zone cut) What do they mean, exactly? And should I be worrying about them? The

Re: "can't validate existing negative responses (not a zone cut)" messages

2010-10-22 Thread Tony Finch
On Sun, 3 Oct 2010, Chris Thompson wrote: > > Oct 3 16:53:10 dnssec: warning: validating @14c9cd70: > 98.206.101.95.IN-ADDR.ARPA PTR: > can't validate existing negative responses (not a zone cut) > > What do they mean, exactly? And should I be worrying about them? > They all seem to refer to PTR

"can't validate existing negative responses (not a zone cut)" messages

2010-10-03 Thread Chris Thompson
Since upgrading our main recursive nameservers to BIND 9.7.2-P2 (and using a trust anchor for the root and lookaside via dlv.isc.org) I am seeing a scatter of warning messages like this: Oct 1 19:47:19 dnssec: warning: validating @1c29d580: 115.197.101.95.IN-ADDR.ARPA PTR: can't validate exist