bind 9.8.2 "no valid signature found"

Running CentOS 6.8 with bind-9.8.2-0.47.rc1.el6_8.4.x86_64 I'm getting lots of log messages of the form Jan 25 22:11:55 janus named[10123]: validating @0x7f51084b6450: cloudflare.com A: no valid signature found CloudFlare's DNSSEC seems to be OK according to http://dnssec-debugger.verisignlabs.c

Re: filter-aaaa-on-v4 does not filter AAAA if there is no existing A Record with the same FQDN - working as designed?

In message <823d435a-eff7-48eb-b99f-b0e36c232...@googlegroups.com>, addie write s: > So we can assume that this is working as designed?! > However, it would be very interesting to know why this policy does not filter > Records when there is no A record. From my point of view this policy is >

Re: filter-aaaa-on-v4 does not filter AAAA if there is no existing A Record with the same FQDN - working as designed?

So we can assume that this is working as designed?! However, it would be very interesting to know why this policy does not filter Records when there is no A record. From my point of view this policy is useless. If we want to prevent clients from receiving any Records for every case, th

Question on Bind validating resolver

Hi, when my Bind resolver tries to get the A record for info.nominet.uk the syslog gets lots of messages like this: Jan 25 21:15:52 box named[25097]: DNS format error from 173.245.58.93#53 resolving info.nominet.uk/DS: invalid response Jan 25 21:15:52 box named[25097]: error (FORMERR) resolving

Re: Bind Queries log file format

Hi Michael On Wed, Jan 25, 2017 at 09:11:41AM -0500, Michael Dahlberg wrote: > Mukund: > > Yea, I can respect that. However, I'm not confident that dropping it right > in the middle of the log entry was the best place for it. I have a number > of processes that monitor the query logs (it seems

Re: Bind Queries log file format

On Wed, Jan 25, 2017 at 8:51 AM, Mukund Sivaraman wrote: > > > Rememeber that not only users, but even us developers have to look at > your logs when you send them to us. > > When things are fine, the sun is shining, hay is growing.. all's fine, > and the fields in the log format that a user want

Re: Bind Queries log file format

On Wed, Jan 25, 2017 at 08:37:45AM -0500, Alan Clegg wrote: > On 1/25/17 7:44 AM, Steven Carr wrote: > > On 25 January 2017 at 10:59, Tony Finch wrote: > >> It's the address in memory of the data structure representing the client. > >> It is mentioned in the CHANGES file (#4471) and in the release

Re: Bind Queries log file format

On 1/25/17 7:44 AM, Steven Carr wrote: > On 25 January 2017 at 10:59, Tony Finch wrote: >> It's the address in memory of the data structure representing the client. >> It is mentioned in the CHANGES file (#4471) and in the release notes - see >> https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.gi

Re: Bind Queries log file format

On Wed, Jan 25, 2017 at 12:44:21PM +, Steven Carr wrote: > On 25 January 2017 at 10:59, Tony Finch wrote: > > It's the address in memory of the data structure representing the client. > > It is mentioned in the CHANGES file (#4471) and in the release notes - see > > https://source.isc.org/cgi-

Re: Bind Queries log file format

On 25 January 2017 at 10:59, Tony Finch wrote: > It's the address in memory of the data structure representing the client. > It is mentioned in the CHANGES file (#4471) and in the release notes - see > https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=c4b7db49326be650fa95a7ede6e

Re: Bind Queries log file format

Michael Dahlberg wrote: > I can discern what almost all of the fields signify except for the > part "@0x7f6450002ef0". It's the address in memory of the data structure representing the client. It is mentioned in the CHANGES file (#4471) and in the release notes - see https://source.isc.org/cgi-b