Bind Queries log file format

Mukund Sivaraman muks at
Wed Jan 25 13:30:34 UTC 2017

On Wed, Jan 25, 2017 at 12:44:21PM +0000, Steven Carr wrote:
> On 25 January 2017 at 10:59, Tony Finch <dot at> 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
> >;a=commitdiff;h=c4b7db49326be650fa95a7ede6e066bbe1268561
> >
> > though the pointer field first turned up in
> >;a=commitdiff;h=a26a62cef2adba0520c5955d740fc75fa7f2c7f5
> Question back to the BIND team... why? what is the purpose of having
> this value exposed in query logs? what exactly is it adding? If it was
> a debug log then I can understand the need to have the memory address
> exposed, but for the "regular" user what is the use case?

When debugging problems, we look at logs. The pointer value is like a
tag or label that uniquely identifies the client object. Client objects
are recycled (reused) in named, and we look for their "identity" to
separate them from others.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <>

More information about the bind-users mailing list