All features
DNS

DNS monitoring: resolution checks, record assertions and change detection

Resolve a name from every region, assert the answer you expect, and get told the moment a record changes. PulseTrace's DNS monitor catches the moved A record, the dropped MX and the propagation that only half finished.

Each check resolves the record type you choose (A, AAAA, CNAME, MX, TXT, NS, SOA, SRV …) against the resolver you choose — a public resolver, your provider's authoritative servers, or both — and compares the answer to your expectation. Resolution time is recorded, so a slow authoritative server shows up as latency, not just failure.

The fingerprint of every answer is kept. When it changes — even to something that still resolves — a change event opens on the timeline with the before and after, and the Regional Intelligence view shows which regions see which answer.

  • All common record types with expected-value assertions.
  • Regional answers — see propagation and geo-DNS behaviour per region.
  • Change detection on every answer, not only failures.
  • DNSSEC validation through the Domain Security monitor.
latency · anomaly episode

How it works

  1. 1Add a DNS monitor: name, record type, expected value (optional), resolver.
  2. 2Each region resolves and compares; timing and the full answer are stored.
  3. 3A mismatch opens an incident; a changed answer opens a change event.

Plan availability

DNS monitor on every plan · change detection and Regional Intelligence on Team and above.

Compare plans →

Monitor types that use it

Questions about dns monitoring

Can I check against my authoritative nameservers?
Yes — set the resolver per monitor, or add two monitors (authoritative and a public resolver) to see propagation lag between them.
Will I be alerted if the record changes but still resolves?
Yes, as a change event with the old and new answers; you can promote changes to incidents per monitor or leave them as timeline entries.