InfoFounding Members35 lifetime licenses available: view the offerInfoMCP launch announcementConnect Claude, Cursor or any MCP client with your API token to let an agent create monitors, manage incidents and configure alerts. Read the docs
Back to blogguides

How to check nameservers and DNS records before they become an outage

2 min read

DNS failures are the worst kind of outage: your servers are fine, your monitoring is green, and half the internet cannot reach you anyway. Here is how to actually verify your nameservers and records instead of assuming the registrar got it right.

What breaks, in order of pain

Expired domain. The registrar fails to renew or the card on file died. The domain drops into redemption and your site vanishes everywhere at once. Set a renewal reminder independent of the registrar's own emails — the reminder email going to a dead inbox is a real failure mode.

Wrong or stale NS records. You moved DNS providers and the delegation at the registrar still points at the old ones. Works fine until the old provider deletes the zone. dig NS yourdomain.com shows who the world thinks is authoritative.

TTL traps. You lower TTL to 60 seconds for a migration, move the record, then forget it there. Every resolver hammers your nameservers and each record change propagates slower than the 24-hour TTL it replaced.

Propagation confusion. DNS does not propagate, caches expire. A record can resolve correctly for you while users on a different resolver see the old answer for hours. Checking from one location proves nothing.

Checking your setup

dig NS yourdomain.com +short shows your delegated nameservers. dig A yourdomain.com @8.8.8.8 and the same against another resolver shows whether answers agree. For the full picture — nameservers, A/AAAA/CNAME/MX/TXT records, plus SSL certificate status — our free DNS & SSL checker runs the whole lookup in one shot.

The part nobody automates

Most teams check DNS once during setup and never again. The failure modes above all happen months later, silently. A DNS monitor watches your actual records continuously and alerts the moment a record disappears, changes unexpectedly, or your certificate drifts toward expiry — the same checks you just ran by hand, running every minute without you.

FAQ

How do I check which nameservers my domain uses?

Run dig NS yourdomain.com +short, or use an online DNS lookup tool that shows NS records alongside A, MX, TXT and other record types.

How long does DNS propagation take?

DNS does not propagate — caches expire. Changes appear as each resolver's cached copy ages out, bounded by the record's TTL, typically minutes to 48 hours.

Can a domain expire even with auto-renew on?

Yes. Auto-renew fails when the payment card on file expires or the registrar account has issues. Independent expiry monitoring catches this before the domain drops.

Keep reading