DNS

The domain name system turns a hostname into an address, and a slow or filtered lookup can make a healthy server look slow.

Definitions only — a term explained here is not a service we sell.

DNS resolves a domain name to an address before any connection starts. Slow or filtered resolving happens before the request leaves the device, so a healthy server can look slow.

A stub resolver asks a recursive resolver, which walks from the root to the authoritative server and caches the answer for the record's time to live (TTL).

Why it looks like a slow site

A first lookup adds a round trip before the connection starts. A slow resolver, a long CNAME chain or an expired TTL during a migration can look slow while the server is healthy. It shows up as high TTFB with a fast server.

Answers vary by resolver location and geo-steering, so one local test is weak proof. Resolve from several networks, compare latency and TTL, and query the authoritative servers directly. The China readiness check includes resolution from different vantage points.

FAQ

What is a TTL?

The number of seconds a resolver may cache a record. Short TTLs make changes faster and raise query volume; long TTLs do the opposite.

Why do different networks get different answers?

Geo-steering, anycast and resolver location all affect the answer. Test from the networks your users use.

Can DNS cause email failures?

Yes. Missing or wrong MX, SPF, DKIM and DMARC records cause rejection or spam placement even when the website resolves fine.

Learn more

Sources

  1. RFC 1034: Domain names, concepts and facilities
  2. RFC 1035: Domain names, implementation and specification
  3. RFC 8484: DNS queries over HTTPS (DoH)