From collectd Wiki
Revision as of 00:50, 28 November 2010 by Octo (talk | contribs) (+Category:Plugins requiring privileges)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
DNS plugin
Type: read
Callbacks: config, init, read
Status: supported
First version: 3.11
Copyright: 2006–2007 Florian octo Forster
2009 Mirko Buffoni
License: GPLv2
Manpage: collectd.conf(5)
List of Plugins

The DNS plugin has a similar functionality to dnstop: It uses libpcap to get a copy of all traffic from/to port UDP/53 (that's the DNS port), interprets the packets and collects statistics of your DNS traffic. The interface it should listen on and whether or not the packets sent by the own host should be collected or not can be set in the configuration file. The details are documented in the collectd.conf(5) manpage.

The metrics collected by this plugin are:

Number of packets with a specific opcode, e. g. the number of packets that contained a query.
Number of queries for each record type. Common record types are for example A, AAAA, MX, and NS.
Number of response codes seen. Common response codes are for example NOERROR (query was successful) and NXDOMAIN (domain or subdomain doesn't exist).
Number of octets sent/received.

Example graphs

Plugin-dns-opcode.png Plugin-dns-qtype.png Plugin-dns-rcode.png Plugin-dns-traffic.png



Since with this plugin acts as a packet sniffer, tools like chkrootkit may start reporting collectd as "suspicious program". Please don't be alarmed – if you load this plugin collectd is supposed to sniff packets. Nothing is done with the sniffed data except counting various aspects of DNS traffic, as you can see in the Example graphs section. But you don't have to take my word for it: Let the source code do the convincing ;)


See also