NSD log support

NSD
1

Hi all,
My colleague is doing some analystic job about authoritative server, BIND’s log is friendly and can be configured flexibly, but we know so far that NSD’s log is designed to write to syslog and though we have specified a explicit log file in nsd.conf, but the content of the log is really simple and lacks query information, we can only get XFR inromation as follows:

[1342414234] nsd[15459]: warning: signal received, reloading…
[1342414234] nsd[15463]: info: memory recyclebin holds 1072 bytes
[1342414234] nsd[15460]: info: NSTATS 1342414234 1342413634 SOA=1 TYPE252=3
[1342414234] nsd[15460]: info: XSTATS 1342414234 1342413634 RR=0 RNXD=0 RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0 SAns=1 SFwdQ=0 SDupQ=0 SErr=0 RQ=3 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=3 SFwdR=0 SFail=0 SFErr=0 SNaAns=3 SNXD=0 RUQ=0 RURQ=0 RUXFR=0 RUUpd=0
[1342414234] nsd[14980]: info: Zone example serial 1342413634 is updated to 1342414234.

Does NSD log contain query information or how can we get more logs from it?

Best regards,
Stuart

2

nsd 3.2.11 has some new options for that:

- - Zone statistics, enable with --enable-zone-stats. This stores the
   BIND8 stats per zone in a configurable statistics file. This option
   does not scale and should therefore not be enabled when serving
   many zones.

Paul

3

a message of 117 lines which said:

Does NSD log contain query information or how can we get more logs from it?

I believe it is a bad idea since formatting the log can take some
server's resources. BIND is not an example to follow, with its
tendency to overbloat (and, even them, the log is not complete, it is
only queries, not answers).

IMHO, this is better done outside of the name servers, with programs
like DNSmezzo <http://www.dnsmezzo.net/&gt; or PacketQ.