DNS Alerts

Understanding alerts

Every DNS change OneDollarDNS detects is recorded as an alert. Alerts tell you exactly what changed, on which host, and when, with the full before and after values.

What triggers an alert

An alert is created any time a DNS check finds records that differ from the host's current snapshot for a given record type. Four types of changes are detected:

Added

A record type or value appeared that wasn't present in the previous snapshot.

Removed

A record type or value that existed previously is no longer returned by the nameserver.

Modified

A record of the same type changed value — for example, an A record pointing to a new IP address.

TTL changed

A record set kept its values, but its TTL changed. Two separate checks confirm the new TTL first, so nameservers that briefly disagree while the change reaches them, or that count a TTL down from a cache as Cloudflare does for flattened CNAMEs, don't cause alerts.

When DNS stops answering

Separately from record changes, you're alerted when a check can't get usable DNS answers at all. A failed check is retried about 5 minutes later, and you're only alerted if it's still failing:

  • Nameservers not responding: none of a set of nameservers is replying. One message covers every domain of yours that uses them, plus any monitored host in a subdomain delegated to them.
  • DNS isn't answering: the nameservers reply, but not with usable answers for a domain, for example because the zone was deleted at your DNS provider.

Both go to your email, and to your Team Notifications channels if you use them, and both are followed by a second message once DNS answers again. A failed check never marks your records as removed, so you won't get a burst of change alerts when things come back.

Registrar nameserver and DNSSEC changes

The nameservers set at your registrar decide which DNS provider answers for your domain. About once an hour, we read them directly from your domain's registry, such as the .com servers, and ask each of those nameservers which NS records it serves. If your domain uses DNSSEC, the same check reads its DS records from the registry and the keys your nameservers serve. Check now runs this too.

  • Nameservers changed: the registry now lists different nameservers for your domain. A second registry server has to agree, or the next check has to see the same change, before you're alerted. The alert shows the old and new lists, and goes to your email and Team Notifications channels.
  • Nameserver mismatch: your registrar lists one set of nameservers, but the nameservers themselves return a different set of NS records. Some resolvers then use servers your registrar doesn't list, which can cause lookups to fail for some visitors and not others. It's rechecked about 5 minutes later before it appears, and shows on the domain page until the two agree. It isn't emailed when it appears, but your weekly summary lists it while it lasts, and it leaves Needs review on its own once it's fixed.
  • DS records changed: the registry lists different DS records for your domain, for example after DNSSEC is enabled or disabled or your DNS provider replaces its signing key. A second registry server has to agree before it's recorded. It appears in DNS Changes for review. When DNSSEC is disabled, or enabled with DS records that match your nameservers' keys, you're also alerted by email and on your Team Notifications channels. A key replacement isn't alerted unless it breaks DNSSEC, which the alert below covers.
  • DNSSEC failing: the DS records at your registrar don't match any key your nameservers serve, or your nameservers serve no keys at all. Resolvers that check DNSSEC, including Google's 8.8.8.8 and Cloudflare's 1.1.1.1, then can't look up your domain. This most often happens after moving to a new DNS provider without updating the DS records at the registrar. It's rechecked about 5 minutes later before you're alerted, and the alert goes to your email and Team Notifications channels. The domain page shows a warning until it's fixed, and the alert leaves Needs review on its own once it is.

We query your nameservers directly, so your hosts are still checked while DNSSEC is failing. We check that a DS record matches a key, but not the signatures on your records, so expired signatures aren't caught.

CDN address changes

CDNs like Cloudflare, Fastly, Akamai, and CloudFront periodically rotate the A/AAAA addresses they serve from their own IP pools. These changes are technically real but rarely actionable, and can generate noisy alerts for domains behind a CDN.

New accounts have Ignore CDN IP rotations turned on by default. It suppresses alerts when A/AAAA records rotate between IPs belonging to the same CDN provider: Cloudflare, Fastly, Akamai, or CloudFront. Real changes, like leaving the CDN entirely or switching from one provider to another, still trigger alerts. Turn it off in your notification settings if you want an alert for every address change.

Suppressed changes are still recorded in your DNS change history and are labeled CDN rotation so you have a full audit trail even when alerts are silenced.

Quick toggle from the DNS Changes page

If the setting is off and changes waiting for review look like routine CDN rotation, they're labeled Likely CDN rotation and a banner on the DNS Changes page lets you enable the setting without leaving the page. Doing so also clears the CDN rotations already waiting.

Muting a host's changes

Some hosts change on a schedule you already expect and don't need an alert for, like a record you're actively migrating or one managed by a process you already trust. You can mute specific record types on a host so their changes stop raising alerts or sending notifications.

Muting is scoped to individual record types on a single host, not the whole domain. Muting A records on one host has no effect on its AAAA or MX records, or on any other host.

A mute can run indefinitely or for a fixed window of 1 hour, 24 hours, or 7 days. A timed mute lifts itself automatically once the window passes, so a temporary mute can't turn into a permanent blind spot you forget about.

Muted changes are still recorded in your DNS change history exactly like any other change. Muting only silences the alert and notification, it doesn't stop monitoring or hide the record from your history.

Muting from the domain page

Open a host's menu on the domain page and choose Mute changes to pick which record types to mute and for how long. A host with an active mute shows a muted badge, and the same menu item becomes Edit muted changes so you can adjust or clear it later.

Alert notifications

When changes are detected, OneDollarDNS immediately sends an email notification to the address associated with your account. The email includes:

  • The affected domain and host name
  • The record type (A, MX, TXT, etc.)
  • The change type (added, removed, modified, or TTL changed)
  • The previous value (for removed and modified records)
  • The new value (for added and modified records)
  • The previous and new TTL (for TTL changes)
  • The time the change was detected

If a single DNS check detects multiple changes across multiple hosts or record types, they are grouped into a single email to avoid inbox noise.

While you have a subscription, you also get a weekly email summary every Monday covering the previous week: how many checks ran, the changes found on each domain, and anything still worth a look, like changes waiting for review, hosts with muted alerts, and nameserver mismatches. It arrives even in a quiet week, as long as your domains were checked. Turn it off under Settings → Notifications.

Want Slack, Discord, or webhook alerts?

The Team Notifications add-on lets you route alerts to Slack, Discord, a generic webhook, or additional email addresses across your account.

Where changes appear

Detected changes appear in three places:

  • DNS Changes: one feed of changes across all your domains, grouped by day. Needs review shows changes you haven't reviewed yet, and All changes is the full record. Filter either view by domain, record type, or time range.
  • Dashboard: your most recent changes across all your domains, with how many still need review.
  • Domain detail page: the changes for one domain, in the same Needs review and All changes views. All changes can be filtered by host.

Domains and hosts each show a status indicator:

Healthy — checked recently, nothing to review.
Needs review — has one or more DNS changes you haven't reviewed yet.
DNS not answering — the nameservers aren't giving usable answers. On a domain, this can also mean only some of its hosts aren't answering.
No nameservers — the registry lists no nameservers for the domain, so nothing can be checked until they are set at your registrar.
Pending — waiting for the first check to complete.
No records — checked, but none of the monitored record types were found.

Reviewing changes

Once you've looked at a change, mark it reviewed to clear it from Needs review. Reviewing a change doesn't delete it; it stays in All changes and on the domain page.

  • Mark reviewed: reviews a single change.
  • Mark all reviewed: on a domain page, reviews every change for that domain. On the DNS Changes page, the button in the top bar shows how many changes it will review: all of them, or only those matching the current filters.

Change history

Every change is kept for as long as your account is active, giving you a full audit trail of DNS changes to your domains. Reviewed changes stay in All changes on the DNS Changes page and in the domain view. Removing a host or domain also removes its history from your account.

Related

  • How It Works — how changes are detected through snapshot comparison.
  • Team Notifications — route alerts to Slack, Discord, webhooks, or additional email addresses.