# DNS Record Types Explained

## How does a browser know where a website lives?

When you type [`www.chaicode.com`](http://www.example.com) into your browser and press Enter, something almost magical happens.

Within milliseconds, your browser figures out **where that website actually lives on the internet** and brings it to your screen.

But here’s the thing  
Computers don’t understand names like [`chaicode.com`](http://google.com).  
They only understand numbers.

So… how does your browser translate a human-friendly name into a machine-friendly address?

That’s where **DNS** comes in.

## What is DNS?

DNS stands for **Domain Name System**.

The easiest way to understand DNS is this:

> **DNS is the phonebook of the internet.**

* You remember a person’s name
    
* Your phonebook stores their number
    
* DNS does the same thing for websites
    

You remember `chaicode.com`  
DNS finds the actual **IP address** like `172.67.213.172`

Without DNS, we’d all be typing long numbers instead of website names—and nobody wants that.

![Explaining DNS Resolution. DNS resolution, or Domain Name System… | by  soulaimaneyahya | Medium](https://miro.medium.com/1%2AgoSb1oow5UBNF3KkzvOX8A.png align="left")

## Why are DNS records needed?

DNS doesn’t store just **one piece of information**.

A website needs to know:

* Which server hosts the website
    
* Which server handles email
    
* Which company manages the domain
    
* Whether the domain is verified for security or services
    

Each of these problems is solved by a **different DNS record type**.

Think of DNS records like **labeled entries in a contact card**:

* Phone number
    
* Email address
    
* Home address
    
* Notes
    

Each record has a specific job.

## What is an NS Record? (Who is responsible for the domain)

**NS** stands for **Name Server**.

An NS record answers this question:

> “Who is in charge of DNS for this domain?”

It tells the internet **which DNS servers are authoritative** for your domain.

### Real-life example

Imagine a post office asking:

> “Which office handles mail for this house?”

NS records point to the DNS provider (like Cloudflare, GoDaddy, Route 53) that controls all other records.

Without NS records, **nothing else works**.

## What is an A Record? (Domain → IPv4 address)

An **A Record** connects a domain name to an **IPv4 address**.

### Problem it solves

Browsers need an IP address to reach a server.

### Example

```plaintext
chaicode.com->172.67.213.172
```

This is the most important record for websites.

### Real-life analogy

* Website name = house name
    
* IP address = house street address
    

Your browser uses the A record to **find the exact house on the internet**.

## What is an AAAA Record? (Domain → IPv6 address)

An **AAAA Record** does the same thing as an A record—but for **IPv6**.

### Why it exists

IPv4 addresses are running out.  
IPv6 was created to fix that.

### Example

```plaintext
example.com → 2606:2800:220:1:248:1893:25c8:1946
```

### Beginner tip

If you understand A records, you already understand AAAA records.  
Same idea. Longer address.

![What is the difference between DNS A and AAAA records? - AccuWebHosting](https://manage.accuwebhosting.com/images/kb/2719_download-36-1.png align="left")

## What is a CNAME Record? (One name pointing to another)

**CNAME** stands for **Canonical Name**.

Instead of pointing to an IP address, a CNAME points to **another domain name**.

### Problem it solves

You don’t want to manage multiple IP addresses.

### Example

```plaintext
www.example.com → example.com
```

Now:

* [`example.com`](http://example.com) has the A record
    
* [`www.example.com`](http://www.example.com) just follows it
    

### Important beginner confusion (A vs CNAME)

* **A record → IP address**
    
* **CNAME → another domain name**
    

A CNAME never points directly to an IP.

## What is an MX Record? (How emails find your mail server)

**MX** stands for **Mail Exchange**.

MX records answer this question:

> “Where should emails for this domain be delivered?”

### Example

```plaintext
example.com → mail.google.com
```

### Real-life analogy

If a letter is sent to your house, the MX record tells:

> “Which post office handles mail for this address?”

### Common confusion (NS vs MX)

* **NS** → Who controls DNS
    
* **MX** → Who handles email
    

They do completely different jobs.

## What is a TXT Record? (Extra information & verification)

**TXT records** store plain text.

They’re often used for:

* Domain ownership verification
    
* Email security (SPF, DKIM, DMARC)
    
* Service validation (Google, GitHub, etc.)
    

### Example

```plaintext
"google-site-verification=abc123"
```

### Think of TXT records as:

Sticky notes attached to your domain saying

> “Yes, I own this”  
> “Yes, this service is allowed”

## A Record vs CNAME Record

### The simple difference

* **A Record** → points **directly to an IP address**
    
* **CNAME Record** → points to **another domain name**
    

## NS Record vs MX Record (They sound related—but aren’t)

### NS Record = DNS authority

NS records answer:

> “Who controls DNS for this domain?”

They point to **name servers** that store all other DNS records.

If NS records are wrong, **nothing works**.

### MX Record = Email delivery

MX records answer:

> “Where should emails for this domain go?”

They only affect **email**, not websites

## How all DNS records work together

Let’s say you own [**example.com**](http://example.com).

Here’s how everything works together:

* **NS records** say who manages DNS
    
* **A / AAAA records** point the website to a server
    
* **CNAME records** connect subdomains like `www`
    
* **MX records** send emails to the correct mail server
    
* **TXT records** verify and secure everything
    

None of these records replace each other.  
They **cooperate**.