DNS Monitoring Explained
Watch meaningful DNS records while understanding resolver caching and expected changes.
Login2Cloud product team · Published 2026-09-27
Monitor the record that matters
A and AAAA records identify addresses, CNAME records alias names, MX records describe mail routing, NS records identify authoritative servers, and TXT records carry policies and verification data. A website migration, mail-provider change or accidental edit can affect different records. Choose the record type that supports the service you want to protect.
Separate lookup from monitoring
A DNS lookup is a snapshot from a resolver. Monitoring repeats observations and can notify when normalized record values change. It does not establish that every recursive resolver worldwide currently has the same answer. TTLs, caching, geographic routing and provider policies can all explain differences.
Choose stable expectations
For a stable service, an expected value can flag an accidental record change. For a CDN or deliberately dynamic endpoint, rigid address equality may create noise. Decide whether you need change awareness or a fixed-value assertion. Document expected changes before migrations and compare the full relevant record set after the work.
Investigate missing or changed records
First confirm the queried name and type. Not every domain needs every record type, so an absent AAAA record is not automatically an outage. Check authoritative DNS and registrar delegation when the result is unexpected. Keep screenshots or change records in your own incident process, without treating old cached answers as definitive current truth.
Connect DNS to service checks
Combine DNS monitoring with HTTP/TCP availability and email-domain checks. That lets you distinguish an address change from an actual service failure and inspect SPF/DMARC configuration alongside mail routing. Use maintenance notifications deliberately during planned changes; do not erase the historical observations.
Common questions
Is a changed IP always an incident?
No. CDNs, load balancing and planned migrations can change addresses legitimately.
Does one lookup show worldwide propagation?
No. It shows the result available to that lookup path at that time.