Prerequisites
Prerequisites
- DevHelm CLI installed or an API token for REST calls
- An API token set as
DEVHELM_API_TOKEN— see Authentication - A domain name to monitor
Create the monitor
Add assertions
Verify that DNS returns the records you expect:| Type | What it checks |
|---|---|
dns_resolves | The domain resolves to at least one record |
dns_expected_ips | Resolved IPs match an expected list |
dns_record_count | Number of returned records matches expectations |
dns_response_time | Query completes within a threshold |
Common use cases
DNS migration validation
DNS migration validation
After changing DNS providers, verify that all regions resolve to the correct IPs. Run from multiple regions to catch propagation issues.
CDN failover detection
CDN failover detection
Monitor CNAME records that point to your CDN. If the CNAME changes unexpectedly, an assertion failure triggers an incident.
MX record monitoring
MX record monitoring
Verify that MX records are present and point to the correct mail servers to catch email delivery issues early.
Next steps
DNS monitor reference
All DNS configuration options and record types.
First alert
Get notified when DNS resolution fails.
Multi-region monitoring
Detect region-specific DNS issues.