// tool/dns-checker
DNS Lookup Tool
Check A, AAAA, CNAME, MX, NS, TXT, SOA, and PTR records without leaving the terminal vibe.
What this is
DNS resolves names to IPs — and a lot of outages are DNS pretending to be something else. This lookup queries the common record types at once so you can spot stale CNAMEs, missing MX entries, broken SPF/DKIM/DMARC, or a TTL that won't let your change propagate.
What it covers
- ›Common record lookups
- ›Propagation sanity checks
- ›TTL visibility
- ›Mail and SPF troubleshooting
Operator notes
- $Check authoritative answers before blaming resolvers.
- $Watch CNAME chains for stale targets.
- $Low TTLs help changes, but cached clients may still lag.
status: Resolver-backed lookups will run through Cloud server functions.
DNS checker
ready
typenamettldata
No records yet.
Frequently asked
- Why is my DNS change not visible yet?
- Caches at recursive resolvers and clients hold the old record until its TTL expires. Lower the TTL (e.g. 300s) before a planned change so propagation is fast when you flip it.
- What records do I need for email to work?
- MX (where mail goes), SPF (TXT — who can send), DKIM (TXT — signing key), DMARC (TXT — policy), and matching PTR on your sending IP. Missing any of these and inbox placement suffers.
- Why can't I put a CNAME on my apex domain?
- CNAME can't coexist with the SOA and NS records that the apex requires. Use ALIAS/ANAME (provider-specific) or an A record instead.