{"id":3416,"date":"2013-12-03T13:52:16","date_gmt":"2013-12-03T19:52:16","guid":{"rendered":"https:\/\/dcmblogmulti.wpengine.com\/?p=3416"},"modified":"2026-10-13T13:04:51","modified_gmt":"2026-10-13T13:04:51","slug":"improving-dns-resolution-time-network-monitoring","status":"publish","type":"post","link":"https:\/\/www.dotcom-monitor.com\/blog\/improving-dns-resolution-time-network-monitoring\/","title":{"rendered":"How to Improve DNS Resolution Time Through Network Monitoring"},"content":{"rendered":"
<\/p>\n
A DNS lookup that takes 300 ms adds 300 ms to every first visit, every API call from a new client, and every uptime check you run. Your web server never sees that time. It shows up as a blank tab before the first byte arrives.<\/p>\n
Most performance work goes into the page itself: images, JavaScript, cache headers, CDN rules. DNS resolution time gets less attention because it happens before any of that, and testing from your own laptop usually returns a cached answer in under a millisecond.<\/p>\n
The lookup is slow for your users, not for you. Monitoring from outside your own network is how you find that out, and how you confirm a fix worked. This guide covers what to measure, how to read the numbers, and which fix matches which symptom.<\/p>\n
DNS resolution turns a hostname like You control step 5, and you control the TTL that decides how often steps 2 through 5 repeat. Your users’ networks control steps 1 and 2. That split is why measuring from your own machine tells you so little: your laptop’s cache and your office resolver are not the ones a customer in Frankfurt uses.<\/p>\n A cached answer from a nearby recursive resolver typically returns in under 20 ms. A full uncached lookup that walks all the way to your authoritative servers is usually acceptable at 50 to 100 ms, and most teams treat anything consistently above 150 ms as worth tracing. These are rules of thumb rather than standards; the right target depends on where your users are and where your nameservers are. Our glossary entry on DNS performance<\/a> covers the metrics in more detail.<\/p>\n Look at the p95 by location rather than a global average. An average of 60 ms can hide a region where every lookup takes 400 ms. And measure the uncached path, the lookup that misses the resolver cache and reaches your nameservers, separately. A resolver cache hit tells you about the resolver, not about your DNS.<\/p>\nwww.example.com<\/code> into an IP address, and it takes anywhere from zero to five network round trips depending on what is already cached along the way.<\/p>\n\n
.com<\/code> servers which nameservers are authoritative for example.com<\/code>.<\/li>\n
What Is a Good DNS Resolution Time?<\/h2>\n