====== Summary ======
The following HowTo describes setting up Zenoss to monitor DNS server queries, defined by domain name and DNS server to query. You will choose which Zenpack and method to implement, setup needed devices, create a [[http://www.zenoss.com/community/docs/zenoss-guide/2.3.0/ch14s02.html|performance template]], combine them to utilize [[http://www.zenoss.com/community/docs/zenoss-guide/2.3.0/ch14s07.html|graphs]] and allow error Events to be returned.

====== What is DNSMonitor and DIGMonitor? ======
DNS and DIGMonitor are [[http://www.zenoss.com/community/docs/zenoss-guide/2.3.0/ch27s01.html|ZenPacks]] that will add a new [[http://www.zenoss.com/community/docs/zenoss-guide/2.3.0/ch14s04.html|DataSource Type]] for you to use. For each datasource you setup, you get a single [[http://www.zenoss.com/community/docs/zenoss-guide/2.3.0/ch14s05.html|datapoint]]: seconds taken to receive query results.

====== Choose a Zenpack ======
Both zenpacks do the same basic thing... lookup and query a DNS server for a domain that you provide it. They each give slightly different data back and each provides slightly different options.

  - DNSMonitor
    * + Allows you to enter a name, and the expected IP address for it to return.
    * + It will generate an event if the returned IP is different.
    * - Cannot easily do different record types
    * See [[../about/dnsmonitor]] for details.
  - DIGMonitor
    * + Allows you to enter a record name, and a port (not in DNSMonitor)
    * + Can easily do different record types
    * - No expected return address. It will not generate an event like above. 
    * See [[../about/digmonitor]] for details.

====== Choose an Implementation Method ======
You may want to do different things with DNS monitoring. Each has benefits. Choose which one you want, and follow its instructions below. Really, both methods can do both things, so just choose one if you are not sure

  - Method 1: Template applied to devices you want to query on
    * + Validity - Verifying that DNS is giving valid results
    * + Scales better - Allows easier replication to many domains
    * + Specified Events - Will let you know that there is a problem with a particular query
    * = Scaling - Easier replication to many domains; All domains to be queried, must be entered as a device
    * - Graphing worse - Each device will have its own seperate graph, NOT conglomerated
    * - Timing worse - not conglomerated in one place per nameserver
  - Method 2: Template applied to nameserver device
    * + Timing - Displays how long DNS queries take in a conglomerated place
    * + Graphing - Allows many domains / URLs to be displayed in one graph
    * - Scales worse - Requires more manual entry if you have lots of domains or nameservers to monitor
    * - Validity & Events - Exists, but many domains can throw an error under the auspices of a single nameserver device


====== Installation ======
  * Download DNSMonitor here: http://www.zenoss.com/community/projects/zenpacks/dnsmonitor
  * Download DIGMonitor here: http://www.zenoss.com/community/projects/zenpacks/digmonitor
  * Zenpack install instructions may be found here: http://www.zenoss.com/community/docs/zenoss-guide/2.3.3/ch25s01.html

FIXME do how to ;-)