DNS tests allow you to proactively monitor the resolvability and lookup times of your DNS records using any nameserver. If resolution is unexpectedly slow or a DNS server answers with unexpected A, AAAA, CNAME, TXT, or MX entries, Datadog sends you an alert with details on the failure, allowing you to quickly pinpoint the root cause of the issue and fix it.
DNS tests can run from managed and private locations, allowing you to run tests on public domains as well as internal services that might be using internal DNS.
By default, only users with the Datadog Admin and Datadog Standard roles can create, edit, and delete Synthetic DNS tests. To get create, edit, and delete access to Synthetic DNS tests, upgrade your user to one of these two default roles.
If you have access to the custom role feature, add your user to a custom role that includes synthetics_read and synthetics_write permissions for Synthetic Monitoring.
After choosing to create a DNS test, define your test’s request.
www.example.com.8.8.8.8, with a fallback on 1.1.1.1 and an internal AWS DNS server.env Tags as well as any other tag to your DNS test. You can then use these tags to quickly filter through your Synthetic tests on the Synthetic Monitoring homepage.Click on Test URL to try out the request configuration. You will see a response preview show up on the right side of your screen.
DNS tests can run:
Assertions define what an expected test result is. When hitting Test URL basic assertions on response time and available records are added. You must define at least one assertion for your test to monitor.
| Type | Record type | Operator | Value type |
|---|---|---|---|
| response time | is less than | Integer (ms) | |
| every record | of type A, of type AAAA, of type MX, of type TXT, of type CNAME | is, contains,matches, does not match | String Regex |
| at least one record | of type A, of type AAAA, of type MX, of type TXT, of type CNAME | is, contains,matches, does not match | String Regex |
You can create up to 20 assertions per API test by clicking on New Assertion or by clicking directly on the response preview:
Set alert conditions to determine the circumstances under which you want a test to fail and trigger an alert.
When you set the alert conditions to: An alert is triggered if any assertion fails for X minutes from any n of N locations, an alert is triggered only if these two conditions are true:
Your test can trigger retries in case of failed test result. By default, the retries are performed 300 ms after the first failed test result-this interval can be configured with the API.
Location uptime is computed on a per-evaluation basis (whether the last test result before evaluation was up or down). The total uptime is computed based on the configured alert conditions. Notifications sent are based on the total uptime.
A notification is sent by your test based on the alerting conditions previously defined. Use this section to define how and what message to send to your teams.
Similar to monitors, select users and/or services that should receive notifications either by adding a @notification to the message or by searching for team members and connected integrations with the drop-down box.
Enter the notification message for your test. This field allows standard Markdown formatting and supports the following conditional variables:
| Conditional Variable | Description |
|---|---|
{{#is_alert}} | Show when the test alerts. |
{{^is_alert}} | Show unless the test alerts. |
{{#is_recovery}} | Show when the test recovers from alert. |
{{^is_recovery}} | Show unless the test recovers from alert. |
Specify how often you want your test to re-send the notification message in case of test failure. To prevent renotification on failing tests, leave the option as Never renotify if the monitor has not been resolved.
Email notifications include the message defined in this section as well as a summary of failed assertions. Notifications example:
Click on Save to save your test and have Datadog start executing it.
You can create local variables by clicking on Create Local Variable at the top right hand corner of your test configuration form. You can define their values from one of the below available builtins:
{{ numeric(n) }}n digits.{{ alphabetic(n) }}n letters.{{ alphanumeric(n) }}n characters.{{ date(n, format) }}n days.{{ timestamp(n, unit) }}n chosen unit.You can use the global variables defined in the Settings and the locally defined variables in the URL, Advanced Options, and assertions of your HTTP tests.
To display your list of variables, type {{ in your desired field:
A test is considered FAILED if it does not satisfy one or several assertions or if the request prematurely failed. In some cases, the test can indeed fail without being able to test the assertions against the endpoint, these reasons include:
CONNRESETDNSINVALID_REQUESTTIMEOUTTIMEOUT can happen.TIMEOUT: The request couldn’t be completed in a reasonable time. indicates that the timeout happened at the TCP socket connection level.TIMEOUT: Retrieving the response couldn’t be completed in a reasonable time. indicates that the timeout happened on the overall run (which includes TCP socket connection, data transfer, and assertions).Additional helpful documentation, links, and articles:
