Record-specific checks
Choose A, AAAA, CNAME, MX, NS, TXT, SOA, PTR, SRV or CAA. Each monitor focuses on one record type for the domain you specify.
Keep names resolving.
Keep services within reach.
Watch the DNS records your services depend on. See lookup results, returned values and TTLs in a focused monitor built for the layer before the connection.
Part of your Uptiva workspace · One workspace. Every signal.
RECORDVALUETTL
A
192.0.2.10300A
192.0.2.11300Illustrative DNS answer · Lookup successful
- Lookup
- example.com
- Record type
- A
- Result
- Records returned
- TTL
- 300 seconds
A healthy server is hard to reach when its name does not resolve. DNS monitoring checks that a selected record lookup succeeds and returns a result, giving you a separate signal for a critical dependency.
Choose the record type you need to watch and review the returned records in the details card. Use distinct monitors for web, mail and other record types so each dependency has a clear status.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
Resolution availability
The check is healthy when the lookup works and returns a result. A failed lookup or missing result gives DNS its own visible failure signal.
Returned records in view
Inspect the type, value and TTL of the records returned by the latest lookup. Keep the actual answer close to the overall monitor status.
DNSSEC context
The details card includes available DNSSEC information alongside the record count. Use it as investigation context when checking the returned result.
A practical check schedule
Choose intervals from five minutes to one day. A schedule suited to DNS gives you regular visibility without treating it like a per-second request stream.
A companion to HTTP checks
Compare DNS status with website, API and IP monitors. Separating these checks makes it easier to see whether the name, network or application needs attention.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Website records
Watch A, AAAA or CNAME lookups for an important hostname. Pair them with website checks to cover resolution and the actual HTTP response.
Email dependencies
Use MX monitors to keep mail routing records in view. Record resolution is one layer of mail availability, separate from whether a mail listener accepts connections.
DNS changes
Review returned values and TTLs around planned updates. Keep the lookup history and results available while records propagate and other service checks continue running.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Choose DNS, enter the domain or record name and select the record type that matters to the service.
- 02
Configure the check.
Choose a supported interval and configure your alert policy. Use separate monitors when you need to watch several record types.
- 03
Follow the signal.
Review the returned records in the details card and compare DNS results with the service checks after a change.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationDoes it check an expected record value?+
The monitor checks that resolution succeeds and returns a result. It does not compare the answer with an expected value. The details card shows the returned values for inspection.
Can one monitor cover all record types?+
Each monitor checks one selected record type. Create separate monitors for the types that matter, such as A for web traffic and MX for email.
What is the shortest check interval?+
DNS monitors support a five-minute minimum interval, with a new monitor starting at fifteen minutes. The form shows the schedules available to your workspace.
Can a DNS change cause a temporary failure?+
Yes. Record changes can take time to propagate. Review the lookup result and consider the consecutive failure setting when short gaps are expected during planned work.
Does this replace domain expiry monitoring?+
No. DNS monitors resolution; domain monitoring checks registration expiry. A domain can resolve today while still approaching a renewal deadline.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring dns monitoring into your workspace.