How to monitor DNS records (A, MX, TXT and more) in Spot Downtime
A step-by-step guide to DNS monitoring: pick the record, list the values you expect, choose a resolver, and get alerted when a record disappears or changes.
· 4 min read · By the Spot Downtime team
A deleted MX record stops your email. A changed A record sends visitors to the wrong server. Neither shows up as an error on your own machines. A DNS monitor looks up your records on a schedule and alerts you when a lookup fails or an expected value goes missing.
Step 1: create the monitor
- Open Monitors, click Add monitor and choose DNS.
- In Domain, enter the name to look up, such as
example.com. A full URL works too; the domain is taken from it. - Pick the Record type: A, AAAA, CNAME, MX, TXT or NS.
- Optionally list Expected values, one per line (see below).
- Optionally set a Resolver, such as
1.1.1.1. Leave it empty for the system default. - Pick how often to Check every, then click Add monitor. The first lookup runs within seconds.
Add a monitor
Domain
example.com
Record
A
Resolver
1.1.1.1
Expected values
203.0.113.10
Step 2: decide what to expect
With no expected values, the monitor only checks that the record resolves. With them, every value you list must be present, so you catch a record that was changed, not just one that was deleted. Up to 10 values; matching ignores letter case and a trailing dot.
| Watch | Record | Expected value |
|---|---|---|
| Your site's server | A | 203.0.113.10 |
| Email delivery | MX | mx1.example.com |
| Your SPF record | TXT | v=spf1 include:_spf.example.com ~all |
| Who runs your DNS | NS | ns1.example-dns.com |
To see what your records hold right now, run:
dig example.com MX +shortOr use the DNS record lookup.
Step 3: read an alert
Expected
203.0.113.10
Got
198.51.100.7
When a value goes missing, the alert shows what came back instead:
expected A record "203.0.113.10", got 198.51.100.7If you just changed the record on purpose, update the expected value. If you didn't, someone else did, or your DNS provider has a problem.
Tips
- Check your own DNS server. Set Resolver to its IP address to check it returns real records, which says far more than a UDP check on port 53.
- Watching a change spread? Point the resolver at a public one such as
8.8.8.8. See DNS propagation explained. - Protect email. Monitor your MX and SPF records; see SPF, DKIM and DMARC explained.
More in this series
Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- How-to · Monitoring · APIsHow to configure gRPC health checkingLearn how to implement and configure gRPC health checking for reliable service discovery and load balancing: server status, Kubernetes probes, client-side health checks, Envoy, cloud load balancers and Consul.November 7, 2026 · 7 min read
- How-to · Servers · MonitoringHow to monitor CPU, memory and disk usage on a Linux serverCheck CPU, memory and disk on Linux with top, free and df, learn which numbers actually matter, pick sensible alert limits, and get alerted before a server runs out.November 4, 2026 · 8 min read