DNS record monitoring for the exact rows in your zone file
Searching “DNS record change” or “TXT drift”? You need per-record expectations, not only “does it resolve.” SitePuls diffs live answers against what you configured so a bad MX or A record becomes an incident before email or traffic routes incorrectly.
Why record-level monitoring is narrower than “DNS health” overall
A wrong A record sends traffic elsewhere; a bad MX breaks mail; TXT changes can break verification flows. These failures can occur while servers stay green.
What SitePuls checks
Record types like A, AAAA, CNAME, MX, TXT, and others depending on your configuration—match expected answers and detect changes.
Compared to domain expiry monitoring
Expiry is about registration dates; DNS monitoring is about the live answers served today.
Compared to website uptime
HTTP monitors see user-visible errors; DNS monitors catch routing mistakes earlier in the chain.
CDNs and multi-provider setups
Assert the CNAME/A records you expect after cutovers; mis-pointing during migrations is common.
Alert channels
Email, Telegram, webhook—same as other monitors.
Compared to /dns-monitoring
Same product area—this page emphasizes “record” and “change” search intent.
Limits
SitePuls isn’t a full DNS hosting UI or DNSSEC lifecycle manager—it focuses on monitoring and alerts.
FAQ
How fast are changes detected?
Aligned with your check interval and plan.
Multiple subdomains?
Create monitors per hostname/record you need.
Private DNS?
Public resolution paths must be checkable from SitePuls’ vantage.
IPv6?
AAAA records can be part of your checks when configured.
Combine with domain expiry?
Yes—both together reduce surprise outages.
TXT for SPF?
If you model TXT expectations, changes will surface when answers differ.
Do you edit zones?
No—SitePuls monitors; you edit DNS at your provider.
How do I start?
Add a DNS monitor with expected records, interval, and contacts.