BEFORE YOU START

DNS changes are observed through several caches and record relationships. Start with the exact record type and name, then confirm where the unexpected answer enters the chain.

FOLLOW ALONGOpen the live DNS Lookup workspace
01

Confirm the queried name and type

An A lookup will not explain an MX or TXT problem. Check the fully qualified name and intended record type.

EXAMPLE
A / AAAA / CNAME / MX / TXT / NS
02

Follow aliases

When a CNAME is present, inspect its target and confirm the target has the required address records.

EXAMPLE
www.example.com → edge.example.net
03

Compare recursive answers

Compare the answer visible from your server with a trusted public resolver and the authoritative DNS provider.

EXAMPLE
dig example.com A
04

Check the consuming service

Email, CDN, certificate, and application systems may cache or validate DNS independently.

EXAMPLE
application-specific verification
Key takeaways
  • Propagation is cache expiry, not a universal countdown.
  • Always query the exact record type and host.
  • A correct DNS answer does not prove the application is configured correctly.