Caches, geographic policies and load balancing can differ legitimately.
DNS DIAGNOSIS
Slow DNS: Separate Lookup Timing from Record Propagation
Distinguish resolution failures, cached answers and two-resolver propagation checks from measurements of your device’s own DNS path.
Slow DNS and different DNS records are different problems. A timing test examines a lookup at a stated vantage point; a propagation check compares returned answers and TTLs. Neither a fast server-side lookup nor matching Google and Cloudflare answers proves that your device’s resolver works correctly.
How to run the check
- Separate names from reachabilityCheck whether several names fail and whether the symptom affects one device or every device. An HTTPS site can fail for certificate or server reasons even when DNS works.
- Read the test locationInternet Analysis’s propagation checker sends DNS-over-HTTPS requests from its server. It does not inspect the resolver configured on your laptop or router.
- Compare record type and TTLChoose the relevant A, AAAA, MX, TXT, NS, CNAME or CAA type. Preserve DNS status, provider and TTL; a missing record type is not automatically a failed domain.Open the relevant tool →
- Evaluate changes with a rollbackIf changing your device resolver, save its original settings and follow official system guidance. Compare repeated lookups; DNS changes do not create more physical bandwidth.
What the signals mean
A returned TTL is not a countdown for every resolver on the internet.
Retry before concluding that records differ or propagation completed.
Frequently asked questions
Does faster DNS make downloads faster?
It can reduce name-resolution delay before a connection starts. Sustained throughput depends on other bottlenecks; changing DNS is not a bandwidth upgrade.
Why do Google and Cloudflare disagree?
Different cache ages, resolver locations, geographic responses or load balancing can produce different records. Compare authoritative configuration and repeat after the relevant cache lifetime.