DNS: A Brief Summary

I’m sure you’ve heard of DNS, but what is it? Why is it so important? And how does it work?

DNS stands for Domain Name System. The original specifications for DNS were published in November 1983. DNS was created as a way to simplify looking up which hosts (servers) have which IP address.

When you access any network or Internet resources using a domain name (such as – your computer needs to translate this to a machine-readable IP address (such as in order to connect to the host containing the resources you’re attempting to access.

Prior to DNS, a technician (or even a user) would need to memorize IP addresses of resources. This method is fine if you only have a handful of servers that you regularly connect to, but what happens when this becomes unmanageable? Back in the days of ARPANET (prior to the Internet as we know it today), the Stanford Research Institute maintained a text file known as HOSTS.TXT which had a mapping of hostnames to host numbers. It looked something like this:


Looks pretty complicated! Back in the ARPANET days host numbers looked like “2/54”, whereas an IP address today would look like “”. This was essentially a text file that could be referenced to know how to access a particular device. For example, if we wanted to access the ACC server from the above excerpt, we would need to reference the file, and find that ACC can be found on network 2, host 54. Then we can access that host.

Managing a text file listing all of this information is hard to do, and a need to automate looking up host numbers (or IP addresses) from hostnames was identified. Thus DNS was born. Fast forward to today, and we use DNS more than we even realize.

When you accessed this page, your device recognized it was attempting to access, so it had to perform a DNS lookup. But how did it know where to look?

Every device is configured with DNS resolvers. These are servers that are either provided by your ISP, maintained internally as part of a corporate network, or are publicly maintained (such as Google Public DNS or Cloudflare DNS). Your device makes a request to these servers. If the server does not have a translation for that particular service cached, it begins the process of looking up the domain.

The DNS resolver will first look up the domain’s NS records (don’t worry, we’ll get to the different types of records in a bit) – these records tell the resolver which DNS server to communicate with. The resolver then establishes a connection to that DNS server and requests the record. If the server is operating correctly and has the record the resolver is requesting, it responds with the data it needs. The resolver then caches the data and passes it along to the device.

Let’s say you’re using Cloudflare’s public DNS servers as your resolvers, and you’re trying to access Your computer will establish a connection to requesting the A record (again, we’ll discuss the types of records in a bit) for doesn’t currently have it cached, so it looks up the NS records for and finds that is the DNS server that it should use. then establishes a connection to and requests the A record for (the same way the computer requested it from It then stores the data locally (to make subsequent requests faster), and delivers the response to the computer, so that the computer can connect as needed. The computer (in most cases) will locally cache the DNS reply so that it can continue to make connections without having to reach out to the DNS resolver each time.

I’ve mentioned DNS record types a few times, such as NS records and A records. There are a few different types, all of which do different things.

A records are Address records. They translate a hostname to an IP address, for example =

NS records are Nameserver records. They delegate which DNS servers should be used for a particular domain.

MX records are Mail Exchanger records. They delegate which mail server is used for incoming mail for a domain (essentially telling someone else’s email system which server to send email messages to).

CNAME records are Canonical Name records. They are essentially aliases for other records. A common use case would be to create an A record for, and have a cname for pointing to

I hope this brief overview of how DNS works was informative! If you have any questions about DNS (or anything else tech related) – please reach out! We’d be happy to answer any questions you may have.


Zack Magee

Zack Magee is the president of Apollo Networks. He comes from a networking, security, and Linux background, and specializes in designing and building computer networks.

Leave a comment

Your email address will not be published. Required fields are marked *