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
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
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
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
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
5 matches
Mail list logo