Ever used your phone’s contacts app? Imagine that, but for the internet. DNS is the internet’s phonebook that maps a site’s URL (like cside.com) to the numeric IP address of the servers hosting that site. Without DNS, we’d have to remember and type those numerical IP addresses for every single website, an impractical task for most humans, given we rely on our phones to save numbers already.
How DNS works
When you visit a website, your browser asks a DNS resolver to find the IP address of the domain you’re trying to visit. This resolver is usually your internet service provider’s DNS server, or a public DNS service like Cloudflare.
If the answer isn’t already cached, the DNS resolver performs a recursive lookup, which goes through the following topology:
- The DNS root server sends the query to the right top-level domain (eg, .dev)
- The top-level domain server points the query toward the domain’s authoritative servers
- The authoritative server provides the final IP address for the domain, sending it back to the resolver to cache and deliver to your browser.
This resolution usually happens in a few milliseconds, but it has to finish before a website can start loading.
DNS Lookup Time
DNS lookup time is the duration from when your system sends a DNS request to when it receives the answer from a lookup server. This usually takes a few milliseconds, but it adds to your page’s load time. Typical queries range from 20 to 120 milliseconds, and “optimal” DNS speed is considered to be under 50 milliseconds.
This speed matters because visitors are waiting before your website even begins to load, bottlenecking the rest of the content until the IP is resolved. Sluggish DNS makes your site feel slower, and if the query times out or fails, users might assume the site is down and give up.
You also have to consider the number of DNS lookups required to load a page. Your browser only does one query per unique domain, but if your site pulls third-party content from many different sites, it has to perform multiple lookups. These queries add up, so limiting the number of external domains on your site reduces this DNS overhead and helps content load quicker.
Why Caching Helps Performance
Lookups don’t have to happen on every single visit, thanks to caching. DNS caching stores the results of DNS lookup queries so that repeat requests for the same domain resolve much faster without contacting external servers.
A DNS record has a value called a TTL, or Time to Live, that describes how long it should be kept in a cache. As long as a cached entry hasn’t expired or changed, the resolver and your device use the saved IP address and skip the full lookup. This gives near-zero lookup delay on the second page load, and cuts down on DNS-related wait time.
