Product Guide
DNS Monitoring vs. Uptime Monitoring: What Each One Actually Catches
A website can stay online while its mail records change, and it can fail while every DNS record stays the same. Here's where DNS change monitoring, website uptime checks, and nameserver reachability checks fit.
November 5, 2026
Your uptime dashboard is green, but someone changed your MX records. Your DNS history is unchanged, but the website is returning errors.
Neither monitoring system has necessarily missed something it promised to check. They may be answering different questions.
The useful comparison starts with the check itself: is it looking at a DNS value, a DNS response, an HTTP response, or an actual user workflow?
What DNS change monitoring asks
DNS change monitoring compares observed records over time. An A record points somewhere new, a TXT value changes, or an MX record disappears.
That can expose configuration drift before a customer reports a symptom. A change to email routing doesn't have to break the website. A CAA edit might affect the next certificate issuance attempt while the current certificate continues working.
It also produces context for investigation: which monitored value changed and what it said before. A change alert alone doesn't determine whether the edit was planned, mistaken, or unauthorized.
What website uptime monitoring asks
A typical website uptime check requests an HTTP or HTTPS endpoint and evaluates the response. Depending on the service and configuration, it may check a status code, response time, expected text, or certificate validity.
Those checks can detect failures behind perfectly valid DNS. A server can be unreachable, the application can return a 500 error, or the TLS certificate can be expired while the address record remains unchanged.
Depth matters. A successful request to the homepage doesn't establish that sign-in, checkout, or background processing works. Checks of those workflows require additional configuration and sometimes a different kind of monitor.
Three incidents that show the difference
Imagine a small business that monitors its website and DNS.
The mail provider configuration is overwritten. An MX record now points to an unintended destination. A homepage check continues to succeed because the website has not moved. A DNS change alert for that MX record gives the team a reason to investigate the mail configuration.
The application crashes after deployment. The website's A and AAAA records still point to the correct server, but requests fail. An HTTP check can detect the failure. Comparing unchanged address records won't explain or repair the application.
The website moves to an unintended server that returns a 200 response. A basic status-code check may pass. A content check could fail if the expected content is absent, and a DNS monitor can report the address change. The outcome depends on what each check is configured to examine.
A sending service stops signing mail. Every DNS record is unchanged and the website is fine, so neither monitor notices. Messages start failing DKIM, and receivers begin routing them to spam. Catching this takes a third kind of monitoring: DMARC aggregate reports, which show how receivers actually evaluated your mail. MyDMARC parses those reports and shows which sources are failing.
These are illustrative scenarios, not a claim that every uptime service or DNS monitor behaves identically. Read the conditions behind each green or red indicator.
Nameserver reachability is a separate check
Records can remain configured correctly while the nameservers stop answering. That is a DNS availability problem, even if there is no record-value change to report.
OneDollarDNS includes nameserver reachability monitoring alongside its record checks. When a check can't get a usable answer, it checks again about five minutes later and only alerts if the problem persists. If every nameserver has stopped replying, one alert covers every domain you monitor on those nameservers.
A successful response through one working nameserver can keep the domain reachable even if another is broken. This isn't a guarantee that every authoritative server has been individually certified healthy. Test each server directly when investigating partial failures.
Caching explains apparently contradictory results
OneDollarDNS checks authoritative answers for record changes. A visitor or uptime probe may reach the website using a recursive resolver's cached answer.
After an address change, monitoring can observe the new value while a website check still uses the previous one. Conversely, cached answers can keep a website reachable for a while during a DNS outage.
That's why an alert timestamp and a customer-visible failure don't always line up. Compare the authoritative answer with public resolvers and inspect TTLs before assuming one monitor is wrong.
Build coverage around what would hurt
For a typical domain, start with critical hostnames and their dependencies:
- Monitor DNS values for the website, mail routing, and authentication records you rely on.
- Check important HTTPS endpoints for availability and meaningful content.
- Add workflow checks where a working homepage isn't enough.
- Keep a way to investigate DNS resolution and authoritative reachability.
- Route notifications to someone who can act on them.
An unchanged CNAME can still point to a retired third-party resource, so ownership reviews remain necessary too. No amount of comparing the same value proves that the destination is still yours.
What OneDollarDNS contributes
OneDollarDNS covers the DNS layer that uptime tools skip. It checks your A, AAAA, CNAME, MX, TXT, NS, CAA, and SRV records directly against your authoritative nameservers, keeps a history of every value, and alerts you when one changes. Nameserver reachability checks are included with every domain.
Checks run hourly by default. Frequent Monitoring checks selected priority hosts every five minutes. Alerts can go to email or, with Team Notifications, to Slack, Discord, or a webhook, which matters when the change you're being warned about is to the MX record for your own inbox.
It isn't an HTTP monitor and won't tell you whether your checkout completes, so pair it with the service checks your application needs. At $1 per domain per month, it costs less than the time it takes to track down one unexplained DNS change. When an alert arrives, the investigation guide helps connect the observed change with account activity and the actual effect on users.
Monitor your DNS for $1/domain/month
OneDollarDNS watches your DNS records and alerts you when anything changes.
Get started free