Dns Resolution Time Budget
Calculator

Inputs

Total resolution time (ms)
80

Results

Total resolution time (ms)
80
Total resolution time (seconds)
0.08
Lookups per second (theoretical)
12.5

Computing results

Total resolution time (ms)80
Total resolution time (seconds)0.08
Lookups per second (theoretical)12.5

formula-map diagram

Total resolution time (ms)
80
Total resolution time (seconds)
0.08
Lookups per second (theoretical)
12.5

Computing relationship

Formula

t = t_root + t_tld + t_authoritative + t_overhead

= 80

Note

This is a simplified model: it applies the standard computing formula to the numbers you entered and ignores protocol overhead, compression variability, retries, contention and other real-world effects. Size your systems with measured data.

Example: with the default inputs, calculator.technology.total_resolution_ms is 80.

More in Technology and computing

See all →

Frequently asked questions

How is the DNS resolution time calculated?+

The calculator adds four values: root server lookup, TLD server lookup, authoritative server lookup and recursive resolver overhead, all in milliseconds. The formula is t = t_root + t_tld + t_authoritative + t_overhead.

What are the default values?+

The defaults are 20 ms for the root lookup, 25 ms for the TLD lookup, 30 ms for the authoritative lookup and 5 ms of resolver overhead, for a total of 80 ms. Replace them with your own measurements to model your setup.

What does the lookups per second figure mean?+

It is 1000 divided by the total time in milliseconds, so it shows how many fully sequential resolutions fit in one second. It assumes each lookup waits for the previous one and does not model parallel queries.

Does this account for DNS caching?+

No. The calculator assumes all three stages are queried one after another with nothing cached. A cached answer would skip some or all stages, so you can set those stage times to a small value to approximate that case.

Can I use this to predict real page load time?+

Only as a rough budget. It sums the numbers you enter and does not measure real network conditions, retries or timeouts, so actual resolution times can differ from the result.