Skip to main content

DNS monitoring

DNS monitoring for resolution failures and record changes.

DNS failures rarely look dramatic in a dashboard until customers cannot reach you. Upwhisper treats DNS as a first-class domain health signal, not a footnote under uptime.

Real dashboard signal

See both outage and configuration drift.

Upwhisper separates “DNS is not resolving” from “DNS records changed”, because those are different operational stories.

Resolution status

A record changes

Nameserver changes

MX changes

What it checks

  • Whether the hostname resolves successfully.
  • A record values, so unexpected address changes are visible.
  • Nameserver changes, which can indicate a planned migration or a serious ownership/control issue.
  • MX record changes, so mail-routing changes do not pass silently.

How alerts work

  • DNS down and DNS recovered events are tracked as stateful incidents.
  • A, nameserver, and MX changes are detected by comparing confirmed check results.
  • Transient lookup gaps are handled carefully so unknown data is not treated as a confirmed change.

Questions buyers ask before trusting a monitor.

Which DNS records does upwhisper track for changes?

The alerting model tracks A records, nameservers, and MX records between confirmed checks.

Does a DNS outage also create an HTTP outage alert?

When DNS and HTTP fail together, Upwhisper avoids double-alerting and explains the combined state in one event.