Core Difference
The main difference between a cached and an uncached DNS test lies in where the DNS data is retrieved. A cached test pulls data from a temporary local storage, while an uncached test forces a fresh retrieval directly from the authoritative source
Cached DNS Testing
When you run a cached DNS test, the system reads data stored from a previous query
- Location: Data comes from the browser, operating system, or local router cache
- Time to Live (TTL): The record remains in the cache until its TTL expiration timer hits zero
- Speed: Retrieval is nearly instantaneous, usually taking between 0 and 5 milliseconds
- Network Traffic: No external traffic is generated; the request never leaves the local network
- Purpose: It simulates what a returning user experiences when visiting a website they recently accessed
Uncached DNS Testing
An uncached DNS test bypasses all temporary storage to request a brand-new copy of the record
- Location: Data is fetched directly from the authoritative DNS nameservers
- Method: The test is performed after flushing the local cache, or by using a tool that queries the server directly
- Speed: Retrieval is slower, often taking 20 to 100+ milliseconds depending on network latency
- Network Traffic: It forces a full recursive lookup across the global internet infrastructure
- Purpose: It measures true propagation status, server performance, and what a first-time visitor experiences
Key Metrics Comparison
| Feature |
Cached Test |
Uncached Test |
| Response Time |
Extremely low (0-5 ms) |
Higher (20-100+ ms) |
| Accuracy |
May show outdated information |
Always shows current server data |
| Path Traveled |
Stays internal to the device/LAN |
Travels across the internet |
| Primary Use Case |
Testing local application performance |
Troubleshooting DNS propagation |
Why the Difference Matters for Testing
1. Verifying DNS Changes