Library › Web & networking

Free guide

DNS for Beginners

Understand how domains find websites and services. DNS stands for Domain Name System. Its job is simple: Turn names people understand into addresses computers can use. Instead of remembering: 104.21.45.12 you can use: example.com DNS helps connect the two.

4 min readFor developers, IT and support staff, business owners and students and beginners

Understand how domains find websites and services.

DNS stands for Domain Name System.

Its job is simple:

Turn names people understand into addresses computers can use.

Instead of remembering:

104.21.45.12

you can use:

example.com

DNS helps connect the two.


1. Think of DNS Like Contacts

Your phone lets you save:

Mum → 0999 123 456

DNS does something similar:

example.com → Server address

So when you visit:

example.com

DNS helps your computer find where that service lives.


2. The Basic Journey

When you visit a website:

You type:
example.com
     ↓
DNS looks up the domain
     ↓
Finds the server
     ↓
Your browser connects
     ↓
Website loads

3. What Is a Domain?

A domain is the human-friendly name:

google.com
nubien.group
example.com

A domain can have different parts:

www.example.com
│   │       │
│   │       └── Top-level domain
│   └────────── Domain name
└────────────── Subdomain

4. The Records You Need to Know

You don't need to memorise every DNS record.

Start with these:

A
AAAA
CNAME
MX
TXT

5. A Record

An A record points a domain to an IPv4 address.

Example:

example.com → 203.0.113.10

Think:

Name → IPv4 address

Commonly used for websites and servers.


6. AAAA Record

An AAAA record points a domain to an IPv6 address.

Think:

A     → IPv4
AAAA  → IPv6

As a beginner, you won't need to configure this as often as an A record.


7. CNAME Record

A CNAME points one domain name to another domain name.

Example:

www.example.com
        ↓
example.com

You might have:

www → example.com

This is useful when multiple names should point to the same destination.


8. MX Record

MX means Mail Exchange.

It tells the internet where email for your domain should go.

For example:

you@example.com
       ↓
     MX
       ↓
Mail server

If your website works but your business email doesn't, check your MX records.


9. TXT Record

A TXT record stores text associated with a domain.

It's commonly used for verification and security.

For example:

Domain verification
Email authentication
Service verification

You may be asked by a service to add something like:

TXT
example.com
"verification=abc123..."

Copy the value exactly as provided.


10. DNS Nameservers

Nameservers tell the internet which DNS system is responsible for your domain.

For example, your domain registrar might show:

Nameserver 1
Nameserver 2

These point your domain to the company managing its DNS records.

Think:

Domain
   ↓
Nameservers
   ↓
DNS records
   ↓
Website / Email / Services

11. DNS vs Domain Registrar

These are different things.

Domain Registrar

Where you register/manage the domain.

Example:

example.com

DNS Provider

Where DNS records are managed.

You can sometimes use the same company for both—or different companies.


12. A Simple Website Setup

Suppose your website is hosted on:

203.0.113.10

You might configure:

Type: A
Name: @
Value: 203.0.113.10

And:

Type: CNAME
Name: www
Value: example.com

Then:

example.com
     ↓
203.0.113.10

www.example.com
     ↓
example.com
     ↓
203.0.113.10

13. Subdomains

You can create separate names under your domain.

For example:

example.com

could have:

www.example.com
app.example.com
api.example.com
mail.example.com

A common setup might be:

example.com       → Website
app.example.com   → Application
api.example.com   → API

14. DNS Propagation

When you change a DNS record, the change may not appear everywhere immediately.

This is called DNS propagation.

You might change:

example.com → New Server

but some users may temporarily still reach the old server.

So:

DNS changes can take time to appear everywhere.

Don't panic immediately after making a change.


15. TTL

TTL means Time To Live.

It tells DNS systems how long they can cache a DNS record.

For example:

TTL: 3600

means approximately:

Cache this information for 1 hour.

Shorter TTL:

  • Changes can be picked up sooner
  • More DNS queries may occur

Longer TTL:

  • Better caching
  • Changes may take longer to appear

16. Common DNS Problems

Website doesn't load

Check:

A / AAAA records
Nameservers
IP address

www doesn't work

Check:

CNAME

Email doesn't work

Check:

MX records

Domain verification fails

Check:

TXT record

You changed DNS but nothing happened

Consider:

Propagation
TTL
Caching

17. Be Careful With DNS

A small DNS mistake can take a website or email offline.

Before changing anything:

1. Know what you're changing
2. Copy the existing value
3. Change only what you need
4. Save
5. Test

Don't randomly delete records because you don't recognise them.


Quick Reference

RecordWhat it does
ADomain → IPv4 address
AAAADomain → IPv6 address
CNAMEName → another domain name
MXDirects email
TXTVerification/security information
NSSpecifies authoritative nameservers

The Beginner DNS Map

Remember this:

                 DOMAIN
                    │
               Nameservers
                    │
              DNS Records
                    │
       ┌────────────┼────────────┐
       ↓            ↓            ↓
     Website       Email       Services
       │            │            │
       ↓            ↓            ↓
      A/CNAME       MX          TXT

You don't need to know everything about DNS.

The Golden Rule:

DNS connects names to services.

And when you're troubleshooting, ask:

"What should this domain point to?"