What Is a Domain Name? How DNS Works

Dhreeti Ranjan BasuNovember 22, 2025

0 1 12 minutes read

If you’ve ever wondered “what is domain name?” or heard terms like DNS, nameservers, A records, or TLDs and felt a little lost—this is your guide. Think of this as domain name explained for beginners: simple where it can be, deep where it matters. By the end, you’ll understand how domains work, how they connect to your website and email, and how to keep your setup fast, reliable, and secure.

We’ll cover the basics, demystify DNS (Domain Name System), walk through the exact steps to connect a domain to a server, and explain how domain structure works (.com, root, TLD, and subdomains). We’ll also clear up the difference between domain and hosting—because that one trips up almost everyone at first.

Whether you’re launching your first site, migrating to a new host, or just curious about what’s going on under the hood, you’re in the right place.

Domain Name Basics

A domain name is the human-friendly address you type into a browser to reach a website—like example.com. Computers use IP addresses (like 203.0.113.10 or 2001:db8::1), but humans prefer words. A domain bridges that gap.

Here are the core ideas to get comfy with:

A domain name points to services (like your website and email) via DNS records.
The domain doesn’t “contain” your website; it simply routes people to the server where your site lives.
You register a domain through a registrar (like Namecheap, Google Domains, Cloudflare, GoDaddy), which works with registries (like Verisign for .com) under ICANN’s rules.

Domain vs URL vs Website

Domain: The name itself (example.com).
URL: The full web address that can include protocol, subdomain, path, query, etc. For example: https://www.example.com/blog?sort=latest
Website: The actual content and files on a web server that your browser loads when you visit the URL.

The difference between domain and hosting (super important)

Domain: Your online address (like a street address).
Hosting: The land and house at that address—your server space, software, and files.

You can own a domain without hosting. You can have hosting without a domain (using an IP or temporary URL), but it’s awkward. Most sites need both: register a domain and point it to your hosting.

Typical combo:

Register domain at Registrar A.
Use DNS hosting at Provider B (could be your registrar, host, or a third-party DNS service).
Point the domain’s DNS records to your web host’s server IP.

Registrars, registries, and ICANN—who does what?

ICANN: The global nonprofit that coordinates domain names and IP addresses.
Registry: The operator for a TLD (top-level domain), e.g., Verisign runs .com.
Registrar: The company you buy the domain from; they interface with registries on your behalf.
Registrant: That’s you, the domain owner.

When you buy a domain, your registrar records your ownership with the registry. You control DNS and contacts via the registrar’s panel (or another DNS provider if you delegate nameservers).

WHOIS, RDAP, and privacy

Every domain has registration data (owner/admin/tech). RDAP (the modern WHOIS) displays this.
For most TLDs, you can enable privacy protection to mask your personal info.
Always use accurate underlying contact details—registrars can lock or even reclaim domains with invalid info.
Turn on registrar lock and 2FA to harden your account against hijacking.

Renewals, transfers, and costs

Most domains cost $10–$40/yr (some TLDs are cheaper, some much pricier).
Domains expire if not renewed—after grace and redemption periods, they can be auctioned or released.
To transfer to another registrar, you’ll unlock the domain and use an EPP/Auth code. Transfers usually extend registration by a year.

Choosing a domain that’s smart for SEO and branding

Keep it short, pronounceable, and easy to spell.
Avoid too many hyphens or numbers—they feel spammy.
Choose a TLD your audience trusts (.com is universal; country TLDs signal locality).
Exact-match keywords in the domain don’t guarantee rankings. Helpful content, technical SEO, and user experience matter more.
If you serve multiple countries, consider .com with hreflang or country-specific ccTLDs (.de, .fr) depending on your strategy.

Subdomains vs subdirectories

Subdomain: blog.example.com (treated like a separate site in many contexts, including cookies and sometimes SEO signals).
Subdirectory: example.com/blog (inherits main domain authority signals more directly).
Use subdomains for distinct products, languages, or apps. Use subdirectories for content sections under the same brand.

www vs non-www

Both are fine. Pick one canonical version for consistency and SEO hygiene:

Set a 301 redirect from the non-canonical to the canonical.
Update DNS (CNAME for www, A/AAAA at apex).
Keep your SSL certificate covering both.

What Is DNS?

DNS (Domain Name System) is the global directory that translates human-friendly names into machine-friendly IP addresses and other service pointers. Without DNS, you’d be typing numbers all day.

At a high level:

You type example.com into your browser.
Your device asks a recursive resolver (often your ISP’s or a public resolver like 1.1.1.1 or 8.8.8.8) for the IP.
That resolver fetches the answer from the authoritative source through the DNS hierarchy if it isn’t cached.

The DNS hierarchy in plain English

Root: The top of the tree (an invisible trailing dot). Root servers know where each TLD lives.
TLD: Top-Level Domain (.com, .org, .net, .app, .uk, etc.). The TLD’s servers know which nameservers are authoritative for your specific domain.
Authoritative nameservers: These hold your domain’s actual DNS records (A, AAAA, CNAME, MX, etc.). They’re the source of truth.

When you register a domain and set nameservers, you’re telling the TLD where to find your domain’s authoritative records.

Recursive resolution: what really happens

Your device asks a recursive resolver for example.com.
If not cached, the resolver asks a root server for .com.
The root returns the .com TLD nameservers.
The resolver asks the .com TLD for example.com.
The TLD returns the authoritative nameservers for example.com (ns1.yourdns.com, ns2.yourdns.com).
The resolver asks those authoritative nameservers for the A/AAAA record.
They reply with the IP address (and TTL). The resolver caches it and returns it to your device.
Your browser connects to that IP and loads the site.

This whole dance usually takes milliseconds, especially with caching.

Caching and TTL (time to live)

Every DNS answer includes a TTL value (seconds) telling resolvers how long they can cache it.
Low TTLs (like 60 seconds) make changes propagate faster but increase DNS query load.
Higher TTLs (like 1–12 hours) reduce load and improve performance but changes take longer to be seen.
“DNS propagation” is mostly caches expiring. Nameserver changes involve the TLD and can take longer (often a few hours, up to 48).

Common DNS record types (the ones you’ll actually use)

A: Points a hostname to an IPv4 address (e.g., example.com → 203.0.113.10).
AAAA: Points to an IPv6 address.
CNAME: Alias one name to another name (www.example.com → example.com, or to a CDN hostname). Not allowed at the apex in standard DNS.
MX: Mail exchange servers for your domain’s email (priority numbers tell the order).
TXT: Freeform text records used for verification (e.g., Google, Facebook) and policies like SPF/DMARC.
SPF (usually a TXT): Defines which servers can send email for your domain.
DKIM (TXT): Public key to validate signed emails.
DMARC (TXT): Tells receivers how to handle failed SPF/DKIM and where to send reports.
NS: Lists authoritative nameservers for the zone. At the apex, these point to your DNS host; subdomain NS records can delegate a child zone.
SOA: Start of Authority—zone metadata (primary nameserver, serial number, default TTL).
SRV: Service records (e.g., for SIP, XMPP).
CAA: Which Certificate Authorities are allowed to issue SSL/TLS certs for your domain.
PTR: Reverse DNS (maps IP → name). Useful for mail servers; set by whoever controls the IP block (your host/ISP), not in your domain’s zone.

A couple of pro notes that are still beginner-friendly:

CNAME at the apex isn’t allowed in plain DNS. Some DNS providers offer ALIAS/ANAME to simulate it safely.
Keep TTLs low (300–600s) while configuring or migrating; raise them later for stability.

DNSSEC in brief (security layer)

DNSSEC adds cryptographic signatures to protect DNS answers from tampering. It prevents certain attacks (like cache poisoning). You:

Enable DNSSEC where your DNS is hosted to sign the zone.
Add a DS record at your registrar (so the parent TLD knows your zone is signed).
Not every setup needs it on day one, but it’s a solid best practice once you’re stable.

Myths and gotchas

“DNS propagation takes 72 hours.” Sometimes, but often changes are visible in minutes to a few hours. Long delays are usually due to high TTLs or nameserver changes.
“A CNAME is faster than an A.” Not inherently. Choose based on architecture needs, not speed myths.
“A domain includes hosting.” Nope. They’re separate products.

How Domains Connect to Servers

Okay, let’s wire things up. This is the practical part—how domains work in the real world when you want your site live.

There are three roles:

Domain registrar: Where you registered the domain.
DNS host: Where your DNS zone (records) lives. This could be your registrar, your hosting provider, or a third-party DNS provider.
Web host/server: Where your website files/app run.

You’ll decide where DNS lives first, then add records that point your domain to your server.

Option A: Keep DNS at your registrar

Pros: Simple, one place to control. Great when your host has a static IP and you don’t need fancy DNS features.
Cons: Fewer advanced features, sometimes slower UI or fewer record types.

Option B: Use your hosting provider’s nameservers

Pros: They often auto-create records; simple if you’re all-in with one host (cPanel, Plesk, managed hosts).
Cons: More vendor lock-in. Migrations mean moving DNS again.

Option C: Use a third-party DNS provider (e.g., Cloudflare, Route 53, DNSimple)

Pros: Fast, globally anycasted DNS; advanced features (ALIAS at apex, traffic steering, geo, health checks, built-in CDN/proxy).
Cons: Slightly more complex. You’ll change nameservers at the registrar.

All are valid. For most beginners, leaving DNS at your registrar or using a reputable managed DNS service is perfect.

The basic records for a typical website

At minimum, you’ll add:

A (and AAAA if you have IPv6) for your apex domain (example.com) pointing to your server IP.
CNAME for www.example.com pointing to example.com (or directly to your host/CDN hostname if advised).
MX records for email (if you’re using email with this domain).
Optional: TXT records for verification (Google Search Console, SSL, email providers).

Example minimal set:

A: example.com → 203.0.113.10 (TTL 300)
AAAA: example.com → 2001:db8::10 (TTL 300) [if supported]
CNAME: www → example.com (TTL 300)

Step-by-step: Point a domain to a server

Add the domain to your web host

In cPanel/Plesk/host dashboard, add example.com as a domain/website.
Note the server IP it gives you (IPv4 and maybe IPv6).
Ensure the web server (Apache/Nginx) has a virtual host/server_name for your domain.

Decide where DNS will live

Stick with the registrar’s DNS or switch nameservers to your DNS provider/host.

Add A/AAAA and CNAME records

A: example.com → your server’s IPv4.
AAAA: example.com → your server’s IPv6 (if available).
CNAME: www → example.com.

If using a CDN or platform host

They may give you a target hostname (like myapp.hosting.example.net). Use CNAME for subdomains.
For the apex, use ALIAS/ANAME (if your DNS supports it) or follow your provider’s instructions (often an A/AAAA via anycast IPs).

Configure SSL/TLS

Use Let’s Encrypt or your host’s certificate tool to enable HTTPS for both apex and www.
Force HTTP→HTTPS redirect. Consider HSTS once you confirm everything works.

Email (optional but common)

If using Google Workspace, M365, or another provider, add their MX records.
Add SPF (TXT), DKIM (TXT/public key), and DMARC (TXT) to improve deliverability.
If running your own mail server, ask your host/ISP to set reverse DNS (PTR) for your sending IP.

Set reasonable TTLs

Use 300–600 seconds while configuring or migrating.
After things are stable, bump to 1–12 hours for fewer queries and better cache performance.

Wait for caches to update and test

DNS changes can be visible in minutes, but allow up to a few hours.
Test with:
- dig/nslookup (e.g., dig A example.com, dig www.example.com)
- Online DNS checkers
- Browser test with cache cleared/private window

Redirect and canonicalize

Choose www or non-www and 301 redirect the other.
Add a canonical tag on pages to match your chosen base URL.
Make sure both hostnames are covered by your SSL cert.

Special cases and pro tips (beginner-friendly version)

Apex and CNAME: Standard DNS disallows CNAME at the apex. Use ALIAS/ANAME or A/AAAA instead.
Cloudflare orange cloud: When proxying, Cloudflare answers with their IPs, not your origin. That’s normal.
Load balancing and failover: Some DNS providers support health checks and traffic steering. Great for high availability.
Geo DNS: You can route users to the nearest region for performance. Advanced, but neat as you scale.
Multiple services under one domain:
- Web: A/AAAA or CNAME for root/www.
- Email: MX, SPF, DKIM, DMARC.
- App-specific: SRV or custom subdomains (api.example.com).
Internal tools: Use subdomains like intranet.example.com and lock them behind VPN/SSO.

Common errors and how to fix them

NXDOMAIN (domain not found): Likely wrong nameservers or the domain not added to DNS.
SERVFAIL: DNSSEC misconfig or upstream issues. Check DS record and zone signing.
Site loads without CSS/JS: Mixed content or incorrect asset URLs after HTTPS switch. Fix absolute URLs, enable HTTPS for assets.
SSL errors: Certificate doesn’t include all hostnames or not yet issued. Re-issue with both apex and www.
“It works on my phone but not my laptop”: DNS cache variance; flush local DNS or wait for TTL expiry.

Domain Structure (.com, root, TLD)

Domains are hierarchical, read from right to left. Understanding the pieces makes everything else click.

The parts of a domain

Root: The top of DNS, represented by a trailing dot (often omitted). A fully qualified domain name (FQDN) technically ends with a dot: example.com.
TLD (Top-Level Domain): The rightmost part, like .com, .org, .net, .app, .uk, .io.
Second-level domain (SLD): The name you register under the TLD, like example in example.com.
Subdomain: A label added to the left of your domain, like www.example.com or blog.example.com.

Examples:

example.com — TLD: .com, SLD: example.
shop.example.co.uk — TLD: .uk, second-level registry zone: .co.uk, SLD: example, subdomain: shop.

Types of TLDs

gTLDs (generic): .com, .org, .net, plus newer ones like .app, .dev, .blog.
ccTLDs (country code): .uk, .de, .fr, .jp. Often used for country-targeted sites.
sTLDs (sponsored/restricted): .edu, .gov, .mil, etc., with strict eligibility.
New gTLDs: Hundreds launched in recent years—great for brand creativity, but choose wisely to avoid user confusion.

Notes:

Some TLDs have special policies. For instance, .app and .dev enforce HTTPS (HSTS preload).
Second-level ccTLD structures (like .co.uk) mean you’re effectively registering the third level (example.co.uk), but it’s your normal domain.

Allowed characters, case, and length

Letters (a–z), digits (0–9), hyphens (-). No spaces or underscores in hostnames.
Case-insensitive: Example.com equals example.com.
Label length: up to 63 characters per label (between dots).
Total length: up to 253 characters for the FQDN (including dots).

Internationalized domain names (IDNs)

Domains can use non-ASCII characters (e.g., café.example). Internally, they’re stored as Punycode (xn--…).
Benefits: Native language domains.
Caution: Homograph attacks (lookalike characters). Buy defensively and ensure your users recognize your brand.

Root servers and anycast

There are 13 named root server letters (A–M), each served by many physical servers globally via anycast.
You never “set” root servers; they’re part of the resolver’s root hints. You do, however, set your domain’s authoritative nameservers at the registry via your registrar.

Apex vs subdomains vs FQDN

Apex: The root of your zone (example.com), also called the “zone apex” or “@”.
Subdomain: Anything left of the apex (www.example.com).
FQDN: Fully qualified name ending with a dot (www.example.com.). Most tools handle the trailing dot implicitly.

DNS delegation

Your TLD (.com) delegates your domain’s authority to your nameservers (NS records at the TLD).
You can delegate a subdomain to separate nameservers (e.g., dev.example.com managed by a different team) by adding NS records for that subdomain in your zone.

How domain structure affects SEO and operations

Pick a TLD your audience trusts. .com still rules, but relevant new gTLDs can work if your brand is strong.
Subdomains can fragment authority; subdirectories usually keep it centralized. That said, use subdomains where it makes operational sense (SaaS apps, regional splits).
ccTLDs can signal country targeting strongly—use them when your content and business are country-specific.

—

Bringing it all together: how domains work

Let’s recap the flow for a real website:

You register example.com at a registrar.
You choose where DNS is hosted (the registrar’s DNS, your host’s DNS, or a third-party DNS service) and set the domain’s nameservers accordingly.
In that DNS provider, you create records:
- A/AAAA for example.com pointing to your server IP(s).
- CNAME for www pointing to example.com (or your platform/edge hostname).
- MX/SPF/DKIM/DMARC if you’re using email on this domain.
Your web server is configured to serve example.com and www.example.com (virtual hosts), with a valid SSL certificate.
Users type your domain; resolvers look up your DNS; the browser connects to your server; the site loads—fast and secure.
You monitor, renew, and adjust TTLs/records as your infrastructure evolves.

Pro tune-ups as you grow:

Enable DNSSEC.
Use a CDN for performance and DDoS shielding.
Add health checks and failover if uptime is critical.
Keep registrar account locked and 2FA-enabled.
Document your DNS changes (zone exports, versioning) for easy rollbacks.

Quick FAQ (because these always pop up)

Do I need hosting to buy a domain? No. You can buy a domain any time and park it or use it for custom email forwarding, etc.
Is .com better for SEO than other TLDs? Not inherently. Trust and click-through can be higher with .com, but rankings depend on content, technical SEO, and links.
How long do DNS changes take? Usually minutes to a few hours. Nameserver changes sometimes take up to 48 hours globally.
Can I use one domain for multiple services? Yes—use subdomains (app., api., mail.) with appropriate DNS records for each service.

Final thought

A domain is the doorway to everything you’ll build online. DNS is the routing system that gets visitors to the right place. Once you grasp the difference between domain and hosting, and how DNS ties them together, the rest—SSL, email, CDNs, performance—becomes much easier to reason about. Start simple, document your setup, and build from there.