A domain is a user-friendly way of referring to the address access a website on the internet. For example, the domain you're reading this on is
vercel.com. Domains can be analogous to the address where your house is. When someone sends a letter to your house, they don't need to know exactly where it is, they just need the address and the relevant post office handles routing the letter.
The system that manages the details about where a site is located on the internet, is known as DNS or the Domain Name System. At its most basic, DNS maps human-readable domain names to computer-friendly IP addresses. When you request a site in your browser, the first step is converting the domain address to an IP address. That process is handled by DNS and called DNS Resolution. Understanding how DNS works is important to ensure that you are configuring your domain correctly.
vercel.comin your browser. Your browser will first check its local DNS cache to see if it knows the IP address of
vercel.com. If it does, it will request the site from that address.
Your browser initiates a DNS query through a server known as a recursive resolver, usually provided by your or a third-party. The recursive resolver acts as a middleman between the browser and DNS server and is used to increase the speed and efficiency of the resolution process. The resolver will check its cache first to see if it already has the IP address. If it doesn't, it'll request the IP address from a DNS server.
There is a network of DNS servers, in a hierarchy, located all around the world. The recursive resolver will query in the following pattern:
- At the entrance to the network are 13 root nameservers. These are the servers that will be contacted first. The root server will look at the domain name, and based on the TLD or top-level domain (.com, .co.uk, etc.), will direct the resolver to the correct TLD server.
- The TLD nameservers store information about domain names that belong to the same TLD. For example, when searching for
vercel.com, once the recursive resolver receives a response from the root nameserver, it will query the
- This TLD server will then respond resolver with details about the authoritative nameserver that has the IP address mapping for
vercel.comstored in an A record. The authoritative nameserver returns this record to the recursive resolver, which will cache the result and return it to your browser.
Once your browser has the IP address, an HTTP request is made by the browser to the web server located at that IP address.
This overview shows a point of view of a user visiting your site. But what does this look like when you're the developer creating a site?
When you've created a Project and deployed it on Vercel, your site lives on Vercel's web servers, which we know to be at the IP address
18.104.22.168. However, your user's browser doesn't know that. For this reason, the browser will perform a DNS Lookup to retrieve the correct IP mapping to
yoursiteaddress.com from a DNS server.
This is where, as a developer, you may have to configure the DNS settings to tell the authoritative server exactly where your site lives. Vercel guides you through exactly what information you need to set, within your Dashboard. There are a number of different settings that you should be aware of:
- DNS records: DNS records are an entry in a database that maps the domain with the IP address, which is then stored on the authoritative server. Some of the most common record types are: CNAME (Canonical name), A (Address), NS (nameserver), and MX (mail exchange). These are all described in more detail in Working with DNS.
- Nameserver: Nameservers are an important part of the DNS. They refer to the actual server that maintains and manages the DNS records. There are three types of nameservers: root nameserver, TLD nameserver, and the authoritative server. You can learn more about using a nameserver with Vercel in Working with nameservers.
- SSL Certificates: SSL Certificates are a way to show that there is a secure connection from your domain to your website. These are described in more detail in Working with SSL certificates.