How does Lemwatch detect DNS record changes?
Lemwatch resolves your A, AAAA, MX, NS, CNAME, and TXT records on every check and hashes them — any hash change triggers a DNS change incident.
Quick answer#
Every scheduled check resolves A, AAAA, MX, NS, CNAME, and TXT records, sorts them, and stores a hash. When the hash changes we log the diff and open a DNS change incident.
Why this matters#
Where to find it in Lemwatch#
Site → DNS — history + latest snapshot.
FAQ#
Do you check all resolvers?#
We query multiple resolvers (Google + Cloudflare) and flag disagreements.
Related#
Previous
How does API endpoint degradation alerting work?
Next
How does Lemwatch track SSL certificate expiry?
Related Articles
Change Detection & Volatility Alerts
Detect sudden performance changes and content modifications.
How does Lemwatch track SSL certificate expiry?
Lemwatch reads the TLS certificate on every uptime check and starts alerting 30, 14, 7, and 1 day before expiry so you never ship an expired cert.
Image Optimisation Checks
Identify oversized, unoptimised, and poorly formatted images on your site.
Font Loading Analysis
Analyse how fonts are loaded on your site and identify performance issues.