DNS Records Guide (with Easy-to-Use Examples)

Posted by

  

Why are DNS records so hard to understand?

DNS is often explained poorly: lists of acronyms, an example line, and the assumption that everything is clear. In reality, DNS records are difficult because they represent abstract concepts, not because they are complex in themselves.

This guide was created with a specific goal:

to truly make you understand, without taking too many things for granted, what ALL the most important DNS records are and what they are used for.

Index of DNS records described in this article:

🔗 Like Techelopment? Check out the site for all the details!

First of all: what DNS really is (without useless technicalities)

The Internet works with IP addresses, not names.

A computer understands:

93.184.216.34

A human understands:

www.example.it

The DNS is a huge phone book that serves to translate readable names into technical addresses.

👉 DNS records are the individual entries in this list.

Each record answers a specific question:

  • Where is this site located?
  • To whom should I deliver emails?
  • Is this name just an alias?
  • Which server manages this service?

Basic structure of a DNS record (key concept)

Every DNS record always has these elements:

  1. Name (e.g., www)
  2. Type (A, AAAA, CNAME, MX, etc.)
  3. Value (IP, domain, text…)
  4. TTL (how long it is stored)

If you understand this scheme, the rest becomes logical.


Record A – The starting point (IPv4)

What it REALLY does

The A record says:

“When someone looks for this name, send them to THIS IPv4 address.”

It does nothing else. It doesn't decide protocols, ports, or anything else.

Example explained

www.example.it → 93.184.216.34

It means:

  1. The user types www.example.it
  2. The DNS responds with an IP
  3. The browser connects to that IP

Why it is so important

Without an A record:

  • the site does not open
  • the domain exists but is unreachable

Typical error

Thinking that:

“The domain points to the server”

In reality, it is the A records that point, not the domain.


Record AAAA – Same concept, different IP (IPv6)

Why it exists

IPv4 addresses are running out. IPv6 solves this problem.

The AAAA record does EXACTLY the same thing as the A record, but with IPv6.

Example explained

www.example.it → 2001:db8:85a3::8a2e:370:7334

If the user's device supports IPv6:

  • it will use the AAAA record

If it doesn't support it:

  • it will use the A record

Fundamental point (often ignored)

👉 A and AAAA are NOT mutually exclusive

A modern domain should have both.


Record CNAME – It's not an IP, it's a referral

The key concept

The CNAME does not point to a server, it points to another DNS name.

It's like saying:

“This name is just a nickname, look at the other one.”

Step-by-step example explained

blog.example.it → www.example.it
  1. The user asks for blog.example.it
  2. The DNS responds: “I don't know, look at www.example.it”
  3. The DNS resolves www.example.it
  4. It obtains the final IP

Why use it

  • avoid duplication
  • connect subdomains to external services

VERY SERIOUS and common ERROR

A CNAME must be the only record on that name.

www → CNAME
www → A


Record MX – Where emails should arrive

Question it answers

“When someone writes to @example.it, to whom should I deliver the email?”

Commented example

MX 10 mail1.example.it
MX 20 mail2.example.it

It means:

  • try mail1 first
  • if it doesn't respond, use mail2

Critical point

The MX record does not contain IPs, but names.
Those names MUST have A or AAAA records.


Record TXT – The most misunderstood record

What it really is

A container for machine-readable information.

Why it is so widely used

Because it is flexible and does not directly affect navigation.

Real case: SPF

v=spf1 include:_spf.google.com ~all

Tells email servers:

“Only Google is authorized to send emails for this domain.”

Real importance

A site can function without TXT records.
Emails cannot, or they will end up in spam.


Record NS – Who commands the domain

Question it answers

“Who is responsible for these DNS records?”

What happens if you change them

Changing NS means:

  • changing DNS provider
  • changing the ENTIRE DNS zone

It is one of the most delicate operations.

What is the DNS Zone?

A DNS zone is the organized set of DNS records that describe how a domain and its subdomains must be resolved on the Internet.


Record SOA – The birth certificate of the DNS zone

Why it exists

It is used to synchronize DNS servers with each other.

It is almost never modified

It is fundamental but rarely touched manually.


Record PTR – The DNS in reverse

Question it answers

“To which domain does this IP belong?”

Why it is crucial

Many email servers reject messages without a valid PTR.


Record SRV – Services, ports, and priority

When it's needed

When knowing an IP is not enough, but also:

  • service
  • protocol
  • port

Used in enterprise environments.


Record CAA – Who can issue SSL certificates

Why it is important today

Prevents SSL certificates from being issued by unauthorized authorities.


Conclusion: why DNS should make sense now

If you now:

  • understand why A and AAAA are similar but different
  • know when to use CNAME and when NOT to
  • comprehend why MX and TXT are vital for emails

then you have truly understood DNS, you haven't just memorized it.



Follow me #techelopment

Official site: www.techelopment.it
facebook: Techelopment
instagram: @techelopment
X: techelopment
Bluesky: @techelopment
telegram: @techelopment_channel
whatsapp: Techelopment
youtube: @techelopment