DNS (Domain Name System) is a naming system for resources connected to the Internet — essentially the phonebook of the Internet.
Monitoring your DNS records helps you ensure that the Domain Name System continues to route traffic properly to your websites, services, and electronic communications.
Why use the DNS Query Telegraf Plugin?
DNS monitoring is done to track DNS requests and servers for performance issues, and therefore keeping an eye on DNS performance at effective levels is a must for companies. Collecting these metrics with the DNS Query Telegraf Plugin will allow you to quickly store them in InfluxDB along with a number of other metrics that can help you gain a comprehensive view of your application, networks and more.
How to monitor DNS Query using the Telegraf plugin
The DNS plugin gathers DNS query times in milliseconds, similar to dig, a network administration command-line tool for querying the Domain Name System (DNS). Configuring the DNS Query Telegraf Plugin requires defining the network protocol, domain, port, and query timeout. Once you point Telegraf to your InfluxDB instance, you can start collecting DNS Query metrics to help you understand performance. You can set thresholds and send alerts to avoid any issues with DNS routing.
Key DNS Query metrics to use for monitoring
Some of the important DNS Query metrics that you should proactively monitor include:
result_code(int, success = 0, timeout = 1, error = 2)
|6||YXDomain||Name Exists when it should not|
|7||YXRRSet||RR Set Exists when it should not|
|8||NXRRSet||RR Set that should exist does not|
|9||NotAuth||Server Not Authoritative for zone|
|10||NotZone||Name not contained in zone|
|16||BADSIG||TSIG Signature Failure|
|16||BADVERS||Bad OPT Version|
|17||BADKEY||Key not recognized|
|18||BADTIME||Signature out of time window|
|19||BADMODE||Bad TKEY Mode|
|20||BADNAME||Duplicate key name|
|21||BADALG||Algorithm not supported|
|23||BADCOOKIE||Bad/missing Server Cookie|