Monitoring
DNS Monitoring
Resolve DNS for a hostname and assert required record types. Stored as monitor kind domain. Pro and above.
Overview
A DNS / domain monitor (kind domain) queries public DNS for a hostname. Success depends on resolution completing within the timeout and required record types returning answers — not on WHOIS or registrar APIs.
Configuration
hostname— public hostname to resolve.timeoutMs— overall probe budget (default5000).recordTypes— types to query (default A, AAAA, CNAME, MX, NS, TXT).requiredRecords— types that must return at least one answer (default["A"]). TXT is never required by default.acceptCnameForAddress— addressability may be satisfied by AAAA/CNAME when true (default).checkDns— defaulttrue.warnDays— reserved for future WHOIS expiry; unused by the DNS provider today.
Results
Missing required records, timeouts, and resolution failures feed DNS health contributors and alerts. Continuous runs need Trigger workers (overview).
Plans
Requires Pro+ (dns_monitor). Free workspaces cannot create DNS monitors.
Limitations
- WHOIS / domain-expiry monitoring is not implemented (
warnDaysis reserved). - Results reflect the resolver path used by Mydle workers — not every recursive resolver worldwide.
- Empty history means the scheduler has not run the rule yet.