We’re excited to announce DNS monitors in Checkly, now available on all plans.
DNS monitors let you track the resolution and lookup times of your DNS records, helping you catch misconfigurations, expired records, and resolver latency issues before your customers do.
➡️ Create your first DNS monitor (and prove that it’s not always DNS)
🔎 Common Use Cases
DNS monitors are useful for:
Detecting when a domain stops resolving to its IP address to prevent downtime.
Verifying records against a specific DNS server (e.g. 1.1.1.1 for Cloudflare) to catch resolver-specific issues.
Monitoring DNS response times to spot slow or inconsistent resolution.
Tracking latency issues across different regions.
🚀 Get Started with DNS Monitors
Jump into your dashboard to add a new DNS monitor.
DNS monitors are also fully integrated into Checkly’s Monitoring as Code (MaC) workflows and available in:
CLI (v6.9.0+): DnsMonitor
Terraform (v1.16.0+): checkly_dns_monitor
Pulumi (v2.7.0+): checkly.DnsMonitor
To get started:
Configure the domain and record type you want to check. 1.
Optionally override the default DNS server (8.8.8.8). 1.
Define assertions on response time, return codes, or specific string matches in the DNS response.
import { Frequency, DnsAssertionBuilder, DnsMonitor } from "checkly/constructs"
new DnsMonitor("dns-monitor", {
name: "DNS A Record Monitor",
activated: true,
frequency: Frequency.EVERY_5M,
locations: ["us-east-1", "eu-central-1"],
maxResponseTime: 800,
degradedResponseTime: 400,
tags: ["dns", "production", "critical"],
request: {
query: "checklyhq.com",
recordType: "A",
nameServer: "9.9.9.9",
port: 53,
assertions: [
DnsAssertionBuilder.textAnswer().contains("3.162.103.33")
],
},
})
👉 Learn more about available configuration options in our developer docs on DNS monitoring.
💬 Connect with Us
Give DNS monitors a try and let us know what you think! We’d love to hear your feedback - drop a comment below or join the conversation in the Checkly community Slack.
Happy monitoring!