> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure DNS probes

> Resolve a record and report resolve time as the metric value.

DNS probes resolve a domain through the agent's DNS resolver and
report the resolution time in milliseconds. Optional value-match
verifies the answer.

## Configuration shape

```json theme={null}
{
  "domain": "api.example.com",
  "record_type": "A",
  "expected_value": "203.0.113.10",
  "resolver": "1.1.1.1"
}
```

## Field reference

| Field | Default | Notes |
| - | - | - |
| `domain` | required | The domain to resolve. |
| `record_type` | `A` | One of `A`, `AAAA`, `CNAME`, `MX`, `TXT`, `NS`, `SRV`, `CAA`, `PTR`. |
| `expected_value` | none | Optional substring match against the resolved record. Mismatch reports `expected_value_mismatch`. |
| `resolver` | system default | Optional override resolver IP. Useful for verifying a specific authoritative server. |
| `timeout_ms` | `5000` | Deadline per DNS attempt, 1 to 60000 ms. |

## Reason codes

The full catalog, with the hint the console shows for each code, is in [Reason codes](https://docs.use.observer/agent/reference/reason-codes.md).

The agent normalises resolver errors into a stable set of codes:

| Reason | Meaning |
| - | - |
| `ENOTFOUND` | The domain does not resolve. |
| `ENODATA` | The name exists but has no records of the requested type. |
| `ETIMEDOUT` | The resolver did not answer in time. Older agents report `ETIMEOUT`. |
| `ESERVFAIL` | The resolver returned `SERVFAIL`. |
| `EREFUSED` | The resolver refused the query. |
| `dns_resolver_invalid` | The `resolver` value is not a valid IP address. |
| `expected_value_mismatch` | Resolution succeeded but the record did not contain `expected_value`. |
| `dns_error` | Other resolver error. |

## Threshold examples

| Goal | Healthy | Unhealthy |
| - | - | - |
| Authoritative answer fast | `under 50` | `over 500` |
| Resolution succeeds at all | `under 5000` | `over 10000` |

When the test is purely "does the domain still resolve",
`unhealthy_value` set to a timeout-equivalent threshold combined
with `no_data` on `ENOTFOUND` covers the case.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.