I got tipped off about this from logwatch report. On my public DNS
server had the following:
Feb 26 04:02:04 onlo named[19336]: validating @0xb2929ee0:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Feb 27 04:02:04 onlo named[32262]: validating @0xb37e25e0:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Feb 27 23:35:37 onlo named[32262]: validating @0xb444ebc0:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Feb 28 04:02:08 onlo named[32262]: validating @0xb444ebc0:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Feb 28 09:37:00 onlo named[32262]: validating @0xb37d9fb8:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Feb 28 18:32:38 onlo named[32262]: validating @0xb4e014e0:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Mar 1 04:02:03 onlo named[32262]: validating @0xb37eac08:
in-addr.arpa SOA: got insecure response; parent indicates it should be
secure
Is this right? Is there some server out there that I hit occationally
that does not have the 'right' in-addr.arpa zone information?
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
