Checking DNS after a change
The most common reason to use a DNS checker is to confirm a change: you updated an A record to point at a new server, switched email providers and replaced MX records, or added a TXT record to verify domain ownership. Because DNS answers are cached, your own computer may keep showing the old values long after the change — a server-side checker like this one queries fresh and shows what new visitors will get.
What to verify, record by record
- A / AAAA: must match your web server or CDN IPs
- MX: must list your mail provider's servers with the right priorities
- TXT: SPF should contain every service that sends mail for you; DKIM and DMARC live on subdomains like
_dmarc.example.com - NS: must point at your current DNS provider — stale NS records are a classic cause of “changes not applying”
Working with raw IPs instead? Use the reverse DNS lookup to map an IP back to its hostname.