Does a name still resolve to what you expect — the right record type, value and across regions.
Every DNS monitor runs on the same spine as the rest of PulseTrace — probed from each region you pick, scored on every check, and streamed into one timeline where incidents open on their own, anomalies surface without a threshold to guess, and reports are generated for you. Point it at a target, choose an interval, and it's watched.
What each check verifies
The panel on the right is the real create-monitor screen — it fills itself in with a DNS example, exactly what you'd type.
For the records that route traffic and mail: the A/AAAA records of your app, the CNAME to your CDN, MX and TXT records, the NS delegation itself. Assert the value you expect and see what each region resolves, so propagation and geo-DNS are visible.
api.example.com A record changed — was 203.0.113.10, now 198.51.100.7 (seen from eu, asia; us-east still 203.0.113.10).