What Is DNS? Explained Simply in 8 Minutes

What Is DNS?

DNS stands for Domain Name System. It is the system that translates a human-readable "domain name" such as plusweb.co into a numeric "IP address" such as 203.0.113.10 — the language computers actually use to talk to each other, since machines on the internet find each other by numbers, not names.

The easiest way to remember it: DNS is like the "internet's phone book." When you want to call a friend, you just remember their name and look up the number — you do not memorize everyone's number. DNS works the same way: you remember only the domain name, and DNS finds the correct IP address for you.

Without DNS, we would have to type long numeric IPs to reach every website, which is impractical. DNS is the fundamental infrastructure that makes the internet as easy to use as it is today.

How DNS Works (Step by Step)

When you type a domain name and hit Enter, a multi-step IP lookup happens behind the scenes in a fraction of a second, across several levels of DNS servers. Here is the rough sequence to get the big picture.

1. 1Your browser checks its local cache first to see whether it already remembers this domain's IP; if so, it uses it right away.
2. 2If not, your device asks a DNS Resolver (usually your ISP's, or one you set yourself, such as 8.8.8.8).
3. 3The resolver queries the Root Server and TLD Server (such as the one that manages .com) to find which nameservers the domain uses.
4. 4It then asks the domain's Authoritative Nameserver, which stores the actual DNS records, and gets the IP address back.
5. 5Your browser takes that IP, connects to the server (hosting), and loads the web page for display.

What Is a DNS Server, and How Many Types Are There?

A DNS server is a server that plays a role in the process of looking up and answering DNS queries — but there is not just one. In reality, several roles work together. Understanding these four main types gives you the full picture of the system.

• DNS Resolver (Recursive) — the intermediary that takes the query from your device and chases down the IP until it has an answer, such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1.
• Root Server — the top level, which points the way to the servers that manage each extension.
• TLD Server — the server that manages each extension, such as the one that knows which nameservers a .com domain uses.
• Authoritative Nameserver — the server that stores your domain's actual DNS records and provides the final answer.

Types of DNS Records You Need to Know (A, AAAA, CNAME, MX, TXT, NS)

A DNS record is a "data entry" that tells where your domain points and what it is configured to do. When you point a domain to hosting or set up email, you will be dealing with these records. The table below summarizes the most common ones.

How to Point a Domain to Hosting or a VPS

After registering a domain, the next task is to "point" it to your server so that typing the domain name reaches your site. There are two main approaches — choose whichever is more convenient.

The first approach is to "set the nameservers" of your domain to point to your hosting provider's nameservers. This is easy and complete, because all records (web, email, etc.) are then managed on the hosting side in one place. The second approach is to keep the existing nameservers and "edit the A record" to point directly to the hosting or VPS IP — ideal when you want to manage DNS on the domain side.

• Method 1 — set your domain's nameservers to your hosting provider's (manage all records at the hosting side)
• Method 2 — keep the existing nameservers and edit the A record to point to the server's IP
• Do not forget to set a CNAME so www points to the main domain, so the site loads both with and without www

How to Change DNS (On Your Device vs. at the Domain)

The phrase "change DNS" has two meanings people often confuse. You need to be clear about where you are changing it, because the results are completely different.

The first is changing the DNS Resolver "on your device," such as setting it to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) to speed up browsing or fix certain sites that will not load. This change only affects your own device — it does not affect anyone else's site.

The second is changing DNS "on the domain side," such as editing the nameservers or DNS records of a domain you own. This affects everyone who visits your site and is used when you want to move hosting or point the domain somewhere new.

• On your device (fixing issues / personal speed): set DNS to 8.8.8.8 or 1.1.1.1 in the network settings of Windows/Mac/mobile
• At the domain (moving/pointing the site): go to the domain management page and edit the nameservers or DNS records to point to the new server

DNS Propagation — Why Changes Do Not Take Effect Instantly

After you change nameservers or edit DNS records at the domain, many people are alarmed that the site has not updated yet. The reason is a process called DNS propagation — the spreading of DNS data to servers worldwide, which takes time.

The cause is that DNS servers and devices "cache" the old data based on the TTL (Time To Live) value. Only once the old cache expires do those systems fetch the new value. As a result, changes may take anywhere from a few minutes to 24-48 hours in some cases to appear everywhere.