DNS Records Explained for Beginners: What They Are, How They Work, and When to Use Them

If you’ve been asked to “update your DNS”, it can feel overly technical at first glance. In reality, DNS records are just instructions that tell the internet where to send traffic whether that’s your website, your email, or a third-party service your business relies on.

This guide walks you through everything you need to know: what DNS records are, how they work, the different types you’ll encounter, and when you might need to use each one.

What Is DNS?

DNS (Domain Name System) is essentially the internet’s directory.

When someone types your domain into a browser, DNS translates that domain into the correct server location. It also helps route email and connect your domain to platforms and tools.

DNS records are the individual entries that control those connections. They are usually stored within what they call a Zone.

The Core Parts of a DNS Record

Most DNS records include the same key fields. Depending on your provider, the labels may vary slightly.

Host (Name)

Defines what part of your domain the record applies to.

@ refers to your root domain (yourbusiness.com)
www refers to a subdomain that is put in front of your root domain (www.yourbusiness.com)
This can also be other subdomains like mail or shop (mail.yourbusiness.com or shop.yourbusiness.com)

Type

The record type (A, MX, TXT, etc.).

Value (Points To / Target / Destination)

Where the record directs traffic.

TTL (Time to Live)

How long in seconds the record is cached before refreshing.

Lower TTL equals faster updates but higher server load. Recommended for rapid updates, site migration, or planned IP changes.
Higher TTL equals more stability. Recommended for stable records like MX (email) or TXT, reducing server requests and increasing performance.

Priority

Used with some records like MX and SRV. Determines which record is used first when there are multiple of the same type.

DNS Record Types (With Real Examples)

Let’s go through the most common DNS record types and exactly how they’re used.

A Record (Address Record)

Purpose:

Points your domain to an IPv4 address (your website server).

Example:

You’re connecting your domain to your website hosting provider.

				
					Host: @
Type: A
Value: 192.0.2.1
TTL: 3600

AAAA Record

Purpose:

Same as an A record, but for IPv6 addresses.

Example:

Your hosting provider supports IPv6 and provides a modern IP address.

				
					Host: @
Type: AAAA
Value: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
TTL: 3600

CNAME Record (Canonical Name)

Purpose:

Points one domain or subdomain to another domain.

Example:

Connecting your domain to Shopify. Also commonly used for platforms like Squarespace, Wix, and Square.

				
					Host: www
Type: CNAME
Value: shops.myshopify.com
TTL: 3600

MX Record (Mail Exchange)

Purpose:

Directs email to the correct mail servers. You’ll often have multiple MX records with different priorities.

Example:

Setting up email with Google Workspace. Also used for Microsoft 365.

				
					Host: @
Type: MX
Value: ASPMX.L.GOOGLE.COM
Priority: 1
TTL: 3600

TXT Record

Purpose:

Stores text for verification and security. TXT records are generally safe to add and won’t disrupt existing services.

Example:

Verifying your domain with a service.

				
					Host: @
Type: TXT
Value: google-site-verification=abc123xyz
TTL: 3600

Or setting SPF for email.

				
					Host: @
Type: TXT
Value: v=spf1 include:_spf.google.com ~all
TTL: 3600

NS Record (Name Server)

Purpose:

Specifies which servers manage your DNS. Usually set automatically, but important when switching providers.

Example:

Pointing your domain to your hosting provider’s DNS.

				
					Host: @
Type: NS
Value: ns1.varialhosting.com
TTL: 86400

SRV Record

Purpose:

Defines specific services, including port and protocol. This tells systems where to find the service and how to connect to it.

Example:

Setting up a VoIP or messaging service (like Microsoft Teams).

				
					Host: _sip._tls
Type: SRV
Value: 100 1 443 sipdir.online.lync.com
TTL: 3600

SOA Record (Start of Authority)

Purpose:

Contains administrative information about your DNS zone. You usually won’t edit this manually.

Example:

Typically looks like this and is auto-managed.

				
					Primary NS: ns1.hostprovider.com
Responsible Party: admin.hostprovider.com
Serial: 2026042301
Refresh: 7200
Retry: 3600
Expire: 1209600
TTL: 3600

PTR Record (Pointer Record)

Purpose:

Maps an IP address back to a domain (reverse DNS). Often configured by your hosting provider.

Example:

Used for email server validation.

				
					IP: 192.0.2.1
Type: PTR
Value: mail.yourbusiness.com

CAA Record (Certification Authority Authorization)

Purpose:

Controls which certificate authorities can issue SSL certificates for your domain.

Example:

Used for an extra layer of security.

				
					Host: @
Type: CAA
Value: 0 issue "letsencrypt.org"
TTL: 3600

Real-World Business Use Cases

Connecting Your Domain to a Website Platform

When using platforms like Shopify, Squarespace, Wix, or Square:

Add A records or CNAME records

Setting Up Professional Email

When connecting Microsoft 365 mail or Google Workspace mail to your domain:

Add MX records
Add TXT records for SPF, DKIM, and DMARC

Verifying Domain Ownership

This is one of the easiest and safest DNS updates:

Add a TXT record provided by the service

A Quick Word of Caution

DNS is powerful—it controls where your traffic goes.

If something is entered incorrectly:

Your website could go offline
Emails might stop working
Services may disconnect

That said, there’s no need to be intimidated.

Adding TXT records is usually safe
Making careful, small updates is manageable
Most platforms provide clear instructions

The key is to double-check before saving and avoid removing records unless you’re certain.

When to Ask for Help

If you’re unsure, don’t guess. Reach out to:

Your developer
Your hosting provider
Your IT team

Even experienced users ask for a second look when needed.

Making the Right Licensing Decision

DNS records aren’t as complicated as they first appear. Once you understand what each type does and how they’re structured, you can confidently handle many common updates yourself.

Start with simple, low-risk changes like TXT records or basic connections. Build from there.

With a bit of practice, you’ll not only understand DNS, you’ll be able to use it to keep your business running smoothly.