tinystats is a filter that reads tinydns logs and stores stats
about query types and errors of your authoritative dns.
This software is inspired by Nate Campi's
system, but tinystats is written in C in order to reduce the amount of resources.
Download the package tinystats-1.1.tar.gz (Perugia, Italy)
To compile do:
tar -xfz tinystats-[version].tar.gz
make install strip
(if you want to modify building and/or installation options, please refer to the top of
If you patched djbdns to enable IPv6, you can define the WITH_IPV6 variable
(e.g. make -D WITH_IPV6 ...).
If you're running FreeBSD you can install tinystats
with his port:
make install clean
Once built and installed, you should modify tinydns/log/run file in order to run tinystats.
The syntax command is:
tinystats [-h] [-s progr] output progr
where output is the directory will contain tinystats.out
(the stats file) and progr is the log receiver (usually multilog).
New log/run file becomes (check tinydns.log.run.sample file
inside the package):
exec setuidgid Gdnslog tinystats -h ./main/tinystats/ \
multilog t n3 s250000 ./main/
If you set -h option, tinystats transforms tinydns logs
into a human-readable form (decimal IP and query type string), here is an example:
192.168.0.50 57552  + MX home.morettoni.local
192.168.0.2 64228  + A current.morettoni.local
192.168.0.2 28675  + ANY morettoni.local
192.168.0.2 51488  + PTR 254.0.168.192.in-addr.arpa
If you use tinydns as a slave of BIND master you can specify -s
option to set the notify manager. When a master server send to tinydns
the notify of zone update into the log, you can find an unimplemented request
(I char) of SOA record (value 0006); tinystats
will run the proper program after -s option with the following parameters:
inside the package you can find an example script (update_slave.sh.sample) useful
to manage updates, the Makefile.sample is a replace version for Makefile
inside tinydns/root: that script merges all data file downloaded from master servers
and rebuilds data.cdb.
- IP of master server that sent the notify;
- the zone to be updated
Example scripts refer to tinydns/root/allow configuration file; this file holds the
slave's zone list and the master server's IP. The syntax is:
You can store zone file in a different directory from tinydns/root simply editing
ZONEDIR variable in both scripts, is important to make *.data, data
and data.cdb files writable to tinydns/log owner user.
The start_slave.sh.sample script downloads all zones listed in allow file,
helpful for the first startup of your slave server.
If tinystats receives ALRM, TERM and HUP signals:
- ALRM: all values in the stats file are set to 0 and the signal is
send to prog;
- TERM: the signal is send to prog;
- HUP: all values in the stats file are set to 0.
tinystats's output file has two lines: the first line has counters
of query types and the second line is a brief explanation of fields.
Here is an example:
First 15 field are self-explanatory, last 6 are:
- total: total number of queries received by tinydns (sum of
first 15 fields and of last 5);
- other: RR not coded in tinystats;
- notauth: tinydns not authoritative for the requested domain;
- notimpl: request not implemented in tinydns;
- badclass: class not implemented in tinydns;
- noquery: empty or error query.
you can build some graphics about queries and errors logged by tinystats,
in the package you can find a shell script (tinydns.sh.sample) that you can
run from your crontab and it reads values and update graphs.
You can configure the script by setting up few variables into the tinydns.conf file
(keep it into the same directory of the script), these variables are:
At the top of the script you can see the default values of this variables.
- TINYSTATS: directory where tinystats stores its stats;
- RRDDB: directory and name of RRD RRD (the script create if at first run);
- OUT: directory where the script puts graphics;
- TYPE: RR list to include in the graph separated by space (for the name
refer to the first 15 fields, but write it uppercase, e.g.: for ns write NS);
- ERROR: error list to include in the graph (the name are the last 5 field, uppercase);
- HTML: set this to 1 to build HTML pages.
Some examples of tinystats in action:
- Manuel Martini: for a lot of hints and testing it into his DNS;
- Riccardo Torrini: for the color hints and the idea of query/error separation;
- Filippo Natali: for the FreeBSD port;
- Riccardo Andreoli: for the corrections of the English page;
- Collin R. Mulliner: for the hints about IPv6;
- Everybody downloads, checks, debugs and uses tinystats!