DNS Uptime Checker

Continuous tracking of authoritative nameserver reachability, query resolution latency, and SOA serial consistency across global vantage points.

No signup

Instant results

100% free

Why DNS Uptime Monitoring Matters

DNS is the critical control plane of the internet (RFC 1034). Micro-outages in nameserver resolution directly correlate with dropped email (SMTP tempfails) and unreachable web endpoints. Without continuous anycast monitoring, regional BGP route leaks or localized DDoS mitigation tactics can cause silent TTL expirations, resulting in global cache misses and NXDOMAIN responses for legitimate requests.

Why It Matters

DNS is the critical control plane of the internet (RFC 1034). Micro-outages in nameserver resolution directly correlate ...

Common Mistakes

Placing all authoritative nameservers in the same autonomous system (ASN) or IP subnet, creating a single point of failure during BGP anomalies.

ANYCAST_NODES

PORT_53_QUERIES

UDP_TCP_RESPONSE

LATENCY_CHECK

UPTIME_ENGINE_V1

ALERT_TRIGGERED

How It Works

Multi-PoP Query Dispatch

Dispatches concurrent DNS queries from multiple geographically distributed Points of Presence to detect regional outages.

Response Consistency Check

Compares query responses across all PoPs to detect split-brain DNS scenarios or anycast routing anomalies.

SOA Serial Monitoring

Tracks SOA serial number changes over time to detect failed zone transfers or unauthorized zone modifications.

Latency & Availability Reporting

Calculates query latency percentiles (p50/p95/p99) and uptime percentage based on historical probe data across all PoPs.

Multi-PoP Anycast Monitoring

Validates DNS reachability across diverse geographic nodes, exposing localized BGP blackholes or regional routing misconfigurations.

SOA Serial Synchronization Checks

Detects stale secondary nameservers by comparing SOA serial numbers across all authoritative nodes, ensuring zone propagation.

EDNS0 & TCP Fallback Validation

Tests response truncation (TC bit) and successful TCP resolution (RFC 7766), vital for large query responses like DNSSEC.

Microsecond Resolution Latency

Tracks fine-grained UDP and TCP response times to detect underlying network congestion or nameserver resource exhaustion.

DNSSEC Chain Verification

Continuously validates RRSIG signatures and DS record delegates (RFC 4033) to prevent localized cryptographic validation failures.

Historical Outage Analytics

Maintains deep historical telemetry of NXDOMAIN, SERVFAIL, and timeout events for root cause analysis of intermittent outages.

Frequently Asked Questions

What constitutes a DNS downtime event?

A downtime event occurs when a nameserver fails to respond within a timeout window (typically 2-5 seconds), returns a SERVFAIL status code indicating internal processing errors, or when all authoritative servers for a zone are unreachable due to network partition.

How does DNS uptime affect email delivery (SMTP)?

MTAs rely on DNS to resolve MX and A records. If DNS is unreachable, MTAs generate 4xx transient errors. Extended DNS outages cause messages to queue and eventually bounce (5xx), directly impacting critical communication delivery.

Why monitor TCP alongside UDP for DNS?

While DNS traditionally uses UDP port 53, RFC 7766 mandates TCP support. When a UDP response exceeds the EDNS0 payload size (e.g., during DNSSEC queries), the TC bit is set, forcing the client to retry over TCP. Failing to support TCP causes silent resolution failures.

What is the impact of inconsistent SOA serials?

If secondary nameservers fail to pull zone updates (via AXFR/IXFR), they serve stale records. This inconsistency leads to unpredictable resolution behavior where some clients receive updated routing information while others receive outdated data, causing partial outages.

How often should DNS infrastructure be polled?

High-availability environments should poll nameservers every 1-3 minutes. This granularity ensures rapid detection of routing anomalies before TTLs expire in downstream recursive resolvers, minimizing the impact radius of an outage.

Does this tool detect regional BGP route leaks?

Yes. By querying from distributed geographic vantage points, the tool identifies when specific PoPs experience elevated latency or timeouts while others remain stable, a common signature of regional anycast routing issues or BGP leaks.

How do TTL values interact with DNS outages?

A high TTL allows caching resolvers to serve stale data during a brief authoritative outage, masking the failure. However, high TTLs delay recovery when changing IP addresses. Proper monitoring allows balancing lower TTLs with robust availability tracking.