DNS MONITORING
Detect DNS record changes and validate them fast
DNS is the routing that points your domain at your website and email. ostr.io WebSec detects DNS record changes and alerts your contacts, so an unexpected edit is validated or restored quickly.
zone change map
Record type, business impact, and provider ownership stay visible together.
DNS records
The records worth watching
DNS monitoring watches a domain's DNS records for changes and alerts a responsible person to review them. ostr.io WebSec monitors A/AAAA, MX, NS, and TXT records as part of its free domain-protection capabilities.
DNS is invisible until it breaks, and then everything breaks at once: the site resolves to the wrong place, email silently stops, or a verification record disappears. ostr.io WebSec monitors DNS record changes as part of its free domain-protection capabilities, presented as free for users on all plans.
- A / AAAA - the addresses your domain resolves to.
- MX - the mail routing that delivers your email.
- NS - the name servers that hold authority for your zone.
- TXT - policy and verification records such as SPF, DKIM, and domain ownership proofs.
| Record type | Business impact if wrong |
|---|---|
| A / AAAA | Website may point to the wrong server or stop resolving. |
| MX | Email delivery can fail while the website still appears normal. |
| NS | DNS authority can move away from the intended provider. |
| TXT | Email authentication, ownership verification, or service setup can break. |
A detected change is a question, not a verdict
Many DNS changes are legitimate: a new mail provider, a migrated host, a fresh verification record. Monitoring exists so that each change is consciously confirmed against work you expected, and so the ones you did not expect surface clearly.
zone change map
Record type, business impact, and provider ownership stay visible together.
Why it matters for a small business
Small businesses often share DNS access across a web developer, a marketing agency, and a hosting provider. With several hands able to edit records, a well-meaning change in one place can break email or routing somewhere else - and nobody notices until a customer reports it. DNS monitoring gives every change a timestamp and an alert, which makes it far easier to connect a problem to the edit that caused it.
The workflow is detection and validation. WebSec reports the change; you confirm whether it was expected; your DNS provider restores or corrects the record if it was not. That clear hand-off keeps response fast and calm.
business impact
Website reachability, email delivery, and customer trust all sit behind these signals.
Example response workflow
Receive the change alert
WebSec reports a monitored DNS record change to your recipients with the time it was observed.Identify the record
Note which record changed - A/AAAA, MX, NS, or TXT - and what it changed to.Validate against expected work
Check whether a migration, new provider, or verification step explains the change.Escalate to your DNS provider
If the change is unexpected, contact the DNS provider to review and restore the correct value.Record the resolution
Document the change and who authorized it so the next alert is quick to triage.
When to contact your DNS provider
- A record differs from your approved configuration and you cannot tie it to expected work.
- Name server (NS) authority changed without a migration you planned.
- Email (MX) routing changed and mail delivery is affected.
- A TXT policy or verification record was removed or altered unexpectedly.
Pair DNS monitoring with domain monitoring for WHOIS context and SSL/TLS monitoring so routing and trust are reviewed together.
owner handoff
Monitoring flags the change; the responsible provider or owner completes the fix.
Why shared DNS access makes monitoring worthwhile
DNS is one of the few systems in a small business that several outside parties can edit, often without telling each other. A web developer points the domain at a new host. A marketing agency adds a tracking subdomain. An email provider asks you to paste in a verification record. Each change is reasonable on its own - but no single person holds the full picture, and a well-meaning edit in one place can break email or routing somewhere else.
That diffusion of responsibility is exactly why a neutral, timestamped record of every change is so useful. Monitoring does not replace coordination between your providers; it gives that coordination a backstop. When something breaks, the first question is always "what changed and when?" - and an alert history answers it in seconds instead of a round of "was it you?" emails.
A practical habit helps here: decide in advance who is allowed to change DNS, and treat any alert that falls outside that group as worth an immediate call. Most alerts will be routine and quickly confirmed. The value is in the rare one that is not - caught early, while it is still a quick fix rather than a customer-reported outage.
It also pays to keep a written record of your intended DNS configuration somewhere everyone can see it. When an alert arrives, comparing the reported change against that reference makes the "expected or not?" decision immediate, and it gives a new developer or provider an authoritative starting point instead of guesswork.
HTTP(S)
Status, timing, output, and Content-Type checks.
WEBSEC
WHOIS, DNS, SSL/TLS, and renewal reminders.
ROUTE
Email and SMS routes for people who can investigate.
Frequently asked questions
What is DNS monitoring?
DNS monitoring watches domain records such as A/AAAA, MX, NS, and TXT for changes, then alerts a responsible person so the change can be validated against expected work.
Does DNS monitoring undo a change for me?
No. WebSec detects monitored DNS record changes and alerts your contacts. Your DNS provider restores or corrects records.
Which records can be monitored?
The records that matter most to routing and delivery - such as A/AAAA, MX, NS, and TXT. Confirm exact coverage and labels in the current ostr.io interface.
Why did I get an alert for a change I made?
That is expected. Every monitored change is reported so it can be consciously confirmed. You simply mark it as expected and move on.
Which DNS changes are most urgent?
Unexpected NS and MX changes usually deserve the fastest review because they can affect authority and email delivery. A/AAAA changes are urgent when website routing is affected.
Start monitoring your DNS
Add your domain, enable DNS monitoring, and assign recipients who can validate a change with your provider.
domain-protection.info is an official monitoring information property by ostr.io. About this site