Supported OS:
Monitor the resolvability of and lookup times for any DNS records using nameservers of your choosing.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.
The DNS check is included in the Datadog Agent package, so you don’t need to install anything else on the server from which you will probe your DNS servers.
Though many metrics-oriented checks are best run on the same host(s) as the monitored service, you may want to run this status-oriented check from hosts that do not run the monitored DNS services.
Edit the dns_check.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your DNS data.
See the sample dns_check.d/conf.yaml for all available configuration options:
init_config:
instances:
- name: Example (com)
# nameserver: 8.8.8.8 # The nameserver to query, this must be an IP address
hostname: example.com # the record to fetch
# record_type: AAAA # default is A
- name: Example (org)
hostname: example.orgIf you omit the nameserver option, the check uses whichever nameserver is configured in local network settings.
Restart the Agent to begin sending DNS service checks and response times to Datadog.
Run the Agent’s status subcommand and look for dns_check under the Checks section.
| dns.response_time (gauge) | The response time for DNS query for a given record, tagged by hostname, e.g. 'hostname:example.com'. shown as second |
The DNS check does not include any events.
This agent check tags all service checks it collects with:
nameserver:<nameserver_in_yaml>resolved_hostname:<hostname_in_yaml>dns.can_resolve:
Returns CRITICAL if the Agent fails to resolve the request, otherwise returns UP.
Tagged by hostname and record_type.
Need help? Contact Datadog support.
Mistake in the docs? Feel free to contribute!