The Domain Name System, DNS for short, is one of the most important protocols on the internet, and yet relatively few people understand its purpose. DNS is a protocol which governs how computers exchange data online. Its purpose, simply stated, is to match names with numbers, helping to convert memorable domain names (such as, into an IP address (such as for that your browser can use.

DNS is essentially a map or a phone book of the internet. As each device and website connected to a network has its own IP address, without DNS we would be forced to keep our own records of which domain names match which IP addresses, which would make the internet much more difficult to use!

The purpose that DNS serves, therefore, is relatively straightforward, but the process itself is not, particularly as there are billions of active IP addresses in use, and billions of DNS requests occurring at any given time.

In this article we will aim to explain how the Domain Name System works, explaining each step from the first query to the moment a webpage loads on your browser.

How does DNS Work?

To the end-user, DNS lookup appears to occur instantaneously, requiring no more than the domain name and a tap of the enter key. However, there is plenty of heavy lifting occurring behind the scenes, with the request, in most cases, passing between four servers before finally matching the domain name with the IP address and loading the webpage.

Here are the four servers involved in the DNS protocol:

DNS Recursor – The main function of the DNS Recursor is to receive the initial query and to pass it on to the relevant server.

Root Nameserver – The Root Nameserver takes the first step in resolving the domain name entered in the initial query into an IP address.

TLD Name Server – The Top Level Domain Server (TLD) is where the last portion of an address (e.g. .com) is hosted.

Authoritative Nameserver – In the last step in the process, the Authoritative Nameserver returns the requested hostname (if it has access to it), back to the DNS Recursor resulting in the webpage being loaded.

DNS Recursor

Every DNS request begins with a query. For example, when you enter into your web-browser your browser proceeds to send a query over the internet to find the matching IP address for that domain name. The first step in this process is for the browser to query the DNS Recursor (also known as a recursive resolver) which can be operated by your ISP, a wireless provider, or a third-party. In this first step, the DNS Recursor acts as a middle-man, connecting your query with the relevant IP address to answer the question of which IP address is associated with the initial query.

Root Nameserver

The Root Nameserver is the first type of DNS server that the DNS Recursor talks to on the road to resolving your query. There are 13 sets of root servers in over 300 locations across the globe, and each one holds DNS information about top-level domains such as .com. There are also thousands of servers supporting the Root Nameservers, located according to where internet demand is the highest. The Root Nameserver helps to translate the original text-based query into a language, such as IP addresses, which computers can understand.

TLD Nameserver

The Top Level Domain (TLD) Nameserver provides the next piece in the puzzle by answering the initial query with the IP address of the domain’s name server. Similar to the Root Nameservers, the TLD Nameservers have 4-13 nameservers across many different locations. The main purpose of the TLD is to store the address information for second-level domains (such as

Authoritative Nameserver

The Authoritative Nameserver is the final step in the DNS process. In this step, the Authoritative Nameserver is able to match an IP address with the requested hostname and returns it to the DNS Recursor. Armed with the matching IP address for the initial domain name query, the DNS Recursor is able to tell your browser what the requested IP address is. Finally, your web browser uses the newly learned IP address to reach the website, and to load the webpage you initially requested!

There are exceptions, deviations, and many layers of extra detail to the DNS process, including caching and non-recursive queries. However, the fundamental process is that which we have outlined in this article, where the initial query proceeds through four servers – DNS Recursor; Root Nameserver; TLD Name Server; Authoritative Nameserver – before the matching IP address and domain name are returned to your browser.

If you would like to monitor and enhance the performance of your website, StatusCake provides a suite of website performance monitoring tools which are easy to set-up and use, and provide you with invaluable insights into how your website’s performance is impacting your customers’ experiences.

Click here, to start your free trial today!

Share this

More from StatusCake


The ultimate guide to working with JSON

7 min read Are you a developer? Are you working with JSON or thinking to? You’re going to need this tutorial guide to walk you through everything you need to know about JSON so you can be a pro in no time!


Design Systems – A Storybook & React Tutorial

6 min read In this tutorial, I’ll be using one of the most popular frontend tools for building a design system – Storybook. This works really well with React, so I’ll be setting up a React project with an example component and showing you how to integrate Storybook within that.


Why you should be using a VPN when working from home

2 min read Are you using a VPN whilst you work from home? No? Well, you should definitely get reading this over your tea break; internet safety has never been so important and this is one thing that is quick, easy and effective to use!

clock measuring uptime

The 8 questions people always ask about uptime monitoring

5 min read We get asked questions about uptime monitoring all the time, and we know that Google does too. So we’ve compiled the top 8 questions that are consistently asked so you can get all of your uptime answers, all in one place!