DNS · Foundations

DNS without guesswork

DNS is a distributed cache of delegated data. Troubleshooting becomes easier when you ask who supplied an answer, when it expires, and whether it matches the authoritative source.

A useful mental model

The domain owner publishes records through authoritative name servers. Recursive resolvers fetch and cache those records for clients. A local operating system, browser, or application may add another cache. Two users can therefore receive different answers at the same moment without either response being fabricated.

Checklist

  1. Confirm the exact name.The apex, www, and an API subdomain are separate names.
  2. Inspect the record type.Check A and AAAA independently; follow CNAME chains to their final answer.
  3. Ask the authoritative servers.This shows the published source rather than a recursive cache.
  4. Ask the client’s resolver.Compare its answer and remaining TTL with the source.
  5. Check delegation.Parent-zone name servers and child-zone configuration must agree.
  6. Retest from the affected network.Split DNS and filtering can make a remote test misleading.

Common patterns

Old address after a change

A recursive or local cache may legitimately retain the prior answer until its TTL expires.

Works on one network

Resolvers may have different cache state, IPv6 reachability, or local policy.

Intermittent answers

Multiple authoritative servers may not share the same zone data, or a record set may contain an unhealthy endpoint.

Name resolves, site fails

DNS has completed its job. Continue with TCP, TLS, and HTTP rather than editing records immediately.

Share evidence safely

Hostnames and public IP addresses are often operationally sensitive even when they are not secrets. Redact internal names, private addresses, tokens, and account identifiers before posting diagnostic output.

Next guide

Read a TLS failure

Once the client has an address, verify the secure connection layer.

Continue to TLS