DNS change monitoring
Every hour heyUptime looks up the A, AAAA, CNAME, NS and MX records of each monitored domain and compares them with the last snapshot. A difference is recorded and sent as a "DNS changed" alert. When the site goes down within 24 hours of a change, the outage alert names that change as the likely cause.
Which records, and why these
In short: A, AAAA and CNAME say where the site is; NS and MX say who controls the domain and its mail. Those are what change in a migration gone wrong or a hijack.
TXT records are left out on purpose: verification tokens for mail and search tools churn constantly and would mean alerts about nothing.
| Record | What it controls | A change usually means |
|---|---|---|
| A / AAAA | The address the site is served from | A hosting move, a load balancer swap, or someone pointing the name elsewhere |
| CNAME | Which other name this one follows | A platform migration (for example to a new CDN) |
| NS | Which name servers answer for the domain | A registrar or DNS provider move, or a takeover |
| MX | Where the domain's email goes | An email provider change, or mail being redirected |
How a change is detected
Records are compared as sets, so a change in order or in the time-to-live is not a change. The first lookup for a new monitor only takes the baseline; comparison starts from the second. Changes are kept for 90 days on the monitor page.
A change is also caught the moment a check fails: if the failed request reached an address that isn't in the last snapshot, that is recorded right away rather than waiting up to an hour for the next refresh.
The change as the likely cause
When an incident opens within 24 hours of a recorded change, the alert includes a line like: Likely cause: your domain's DNS records changed 12 minutes earlier (A 203.0.113.10 → 198.51.100.24). The same line appears on the recovery message and on the incident. That is the difference between "it's down" and knowing which setting to look at.
The DNS changed alert
Each detected change goes out to every alert channel with what changed, for example "NS ns1.old-host.com, ns2.old-host.com → ns1.new-host.net, ns2.new-host.net". If you made the change, you can ignore it. If you didn't, check your domain's DNS settings now: it can mean the site or its mail has been pointed elsewhere.
What it is not
This is change detection for the domains behind your monitors, not a general DNS monitoring service. It doesn't query specific name servers, measure resolution time from several places or watch records for domains you don't monitor. It does, however, time the DNS step of every check, so a slow resolver shows up on the monitor page.
Questions
How quickly will I know my DNS changed?
Within an hour in the normal course of things. If the change breaks the site, the failed check catches it in seconds and the down alert names the change.
Will I get alerts when my CDN rotates addresses?
If the A or AAAA records change, yes, once per change. Most CDNs keep the records stable and change the routing behind them; if yours rotates addresses often, the alerts tell you how often.
Does DNS monitoring cost extra?
No. It runs for every website monitor on every plan, including the trial.
Can heyUptime detect a domain hijack?
It can tell you that the NS, A or MX records changed and that the site went down afterwards, which is what a hijack looks like from outside. Acting on it is up to you and your registrar.
Know what changed before you start guessing.
Add your site and its DNS records are snapshotted within minutes and compared every hour from then on. Free for 14 days, no card.
Related
Updated October 8, 2026.