?Can someone give some info if the dnstap-read can be present on Graph like the 
DSC software . I believe dnstap is much more detail but i just want to know if 
this is possible ...

thanks

________________________________
From: dnstap <[email protected]> on behalf of Murray Stokely 
<[email protected]>
Sent: Tuesday, October 25, 2016 6:56 PM
To: [email protected]
Subject: [dnstap] dnstap not writing to unix domain sockets with unbound 1.5.10 
on FreeBSD 11-STABLE.

I'm having trouble getting anything out of dnstap with unbound 1.5.10 on 
FreeBSD 11-STABLE with dustup gocode freshly installed.

I've run the fstrm 0.2.0 unit tests on this box to verify that reading/writing 
to the unix domain sockets is working properly (has anyone evaluated GRPC 
rather than fstrm now that google has released a transport for protocol 
buffers?)


The dnstap section of my unbound.conf is:


dnstap:

  dnstap-enable: yes

  dnstap-socket-path: "/var/run/unbound/dnstap.sock"

  dnstap-send-identity: yes

  dnstap-send-version: yes

  dnstap-log-resolver-response-messages: yes

  dnstap-log-client-query-messages: yes


I'm running unbound in a chroot, but I can't find the socket either in or out 
of the chroot :


server:

  directory: /usr/local/etc/unbound

  chroot: /usr/local/etc/unbound


First I run two dustup listeners (as I'm not sure if its supposed to be inside 
the chroot or not):


dnstap -u /var/run/unbound/dnstap.sock -w /root/dnstap.1

dnstap -u /usr/local/etc/unbound/var/run/unbound/dnstap.sock -w /root/dnstap.2


Then I start unbound:


# sh /usr/local/etc/rc.d/unbound start

Obtaining a trust anchor:.

Starting unbound.

[1477374748] unbound[10467:0] debug: creating udp4 socket 0.0.0.0 53

[1477374748] unbound[10467:0] debug: creating tcp4 socket 0.0.0.0 53

[1477374748] unbound[10467:0] debug: switching log to syslog


unbound works fine, but I am not seeing anything written out to my /root/dnstap 
files.


I spent a little time playing around with ktrace and dtrace but I haven't yet 
really figured out what is going on or why it is not writing out logs.


Any pointers for debugging why messages don't seem to be getting sent to the 
domain socket?  Thanks,


       - Murray


Confidentiality Notice: This email (including any attachment) is intended for 
internal use only. Any unauthorized use, dissemination or copying of the 
content is prohibited. If you are not the intended recipient and have received 
this e-mail in error, please notify the sender by email and delete this email 
and any attachment.
Confidentiality Notice: This email (including any attachment) is intended for 
internal use only. Any unauthorized use, dissemination or copying of the 
content is prohibited. If you are not the intended recipient and have received 
this e-mail in error, please notify the sender by email and delete this email 
and any attachment.
_______________________________________________
dnstap mailing list
[email protected]
http://lists.redbarn.org/mailman/listinfo/dnstap

Reply via email to