can check_bind.sh plugin handle multiple zones?
Posted: Mon Sep 28, 2015 8:17 am
As some of you know, I have been working on the check_bind.sh plugin on a lab DNS server. Had a few issues and now seems all is good. However - my last problem revolved around the plugin returning zero values when it came across stats for multiple zones in the named.stats.tmp file. Like this:
Zone "1"
Zone "2"
I was able to modify the script to ignore the stats from "localhost.localdomain", but if having more than one zone on the DNS server breaks the plugin, what happens when you have hundreds of zones on your DNS server? This is how we have it in production and I can't move forward on this until I can find a solution that works.
Question 1:
Should the script be able to handle multiple zones and still parse out the correct info?
Question 2:
If so, what needs to happen to make this work?
Zone "1"
Code: Select all
[localhost.localdomain]
[155.168.192.in-addr.arpa]
16 queries resulted in NXDOMAIN
16 queries resulted in nxrrset
66 queries resulted in authoritative answer
34 queries resulted in successful answer
Code: Select all
[testdns.net]
++ Zone Maintenance Statistics ++
2167 queries caused recursion
25707 queries resulted in NXDOMAIN
2 queries resulted in SERVFAIL
204 queries resulted in nxrrset
52725 queries resulted in non authoritative answer
66 queries resulted in authoritative answer
26880 queries resulted in successful answer
51384 responses with EDNS(0) sent
52793 responses sent
51384 requests with EDNS(0) received
52793 IPv4 requests received
Question 1:
Should the script be able to handle multiple zones and still parse out the correct info?
Question 2:
If so, what needs to happen to make this work?