A Complete Guide to DNS Records: A, CNAME, MX, TXT & More

By CyclebreezeHost Team ·

The Domain Name System (DNS) is often called the phonebook of the internet, and for good reason. Every time someone types your domain name into their browser, DNS translates that human-readable name into the numerical IP address where your website actually lives. Understanding DNS records gives you control over how your domain routes traffic, delivers email, and verifies your identity across the web.

What Is DNS and How Does It Work?

When a visitor types www.example.com into their browser, their device sends a query to a DNS resolver (usually provided by their internet service provider). The resolver checks its cache for a recent answer. If it does not have one, it queries the authoritative DNS servers for your domain to find the correct records. Once it gets an answer — for example, the IP address 192.0.2.1 — the browser connects to that address to load your website.

This entire process happens in milliseconds and is completely invisible to your visitors. But behind the scenes, DNS records determine exactly where traffic goes.

A Records

An A record (Address record) maps a domain name to an IPv4 address. This is the most fundamental DNS record type and the one you will use most often.

Example: example.com → 192.0.2.1

Use an A record when you need to point your domain or a subdomain directly to a server's IP address. Your primary domain, subdomains like blog.example.com, and any service hosted on a specific IP all use A records.

AAAA Records

An AAAA record is identical to an A record except it maps a domain to an IPv6 address instead of IPv4. As IPv6 adoption continues to grow, adding AAAA records alongside your A records ensures your site is accessible over both protocols.

Example: example.com → 2001:0db8:85a3::8a2e:0370:7334

If your hosting provider supports IPv6 (CyclebreezeHost does), set up both A and AAAA records for full compatibility.

CNAME Records

A CNAME record (Canonical Name record) maps one domain name to another domain name rather than to an IP address. The DNS resolver follows the chain until it finds an A or AAAA record with an actual IP address.

Example: www.example.com → example.com

CNAME records are commonly used to point the www version of your domain to the root domain, to set up subdomains that point to external services (like mail.example.com pointing to a mail provider), and to configure CDN services. One important rule: you cannot place a CNAME record on the root domain (the apex, like example.com without any subdomain prefix) if other records like MX or TXT exist there.

MX Records

MX records (Mail Exchanger records) tell the internet where to deliver email for your domain. When someone sends an email to you@example.com, the sending server looks up the MX records for example.com to find the mail server that should receive the message.

Example: example.com → mail.example.com (priority 10)

MX records include a priority value. Lower numbers have higher priority. If you have multiple MX records, email is delivered to the highest-priority server first, with lower-priority servers acting as fallbacks. This is essential for reliable email delivery.

TXT Records

TXT records store arbitrary text data associated with your domain. While they can technically hold any text, their primary use in modern DNS is for verification and email authentication.

SPF (Sender Policy Framework)

An SPF record is a TXT record that specifies which mail servers are authorized to send email on behalf of your domain. When a receiving server gets an email claiming to be from your domain, it checks your SPF record to verify the sending server is legitimate.

Example: v=spf1 include:_spf.example.com +a +mx ~all

DKIM (DomainKeys Identified Mail)

DKIM uses a TXT record to publish a public encryption key. Your mail server signs outgoing emails with a private key, and receiving servers use the public key in your DNS to verify the signature. This proves the email has not been tampered with in transit.

DMARC (Domain-based Message Authentication, Reporting & Conformance)

A DMARC record is a TXT record that tells receiving servers what to do when an email fails SPF and DKIM checks. It also specifies where to send aggregate reports about email authentication results.

Example: v=DMARC1; p=quarantine; rua=mailto:reports@example.com

NS Records

NS records (Name Server records) identify which DNS servers are authoritative for your domain. These records are typically set at your domain registrar and point to your hosting provider's nameservers.

Example: example.com → ns1.cyclebreezehost.com

When you change your nameservers to point to CyclebreezeHost, you are updating your NS records. All other DNS records are then managed through the authoritative nameservers specified in these NS records.

Understanding TTL

TTL (Time to Live) is not a record type but a value attached to every DNS record. It specifies how long (in seconds) a DNS resolver should cache the record before requesting a fresh copy from the authoritative server.

  • High TTL (86400 seconds / 24 hours): Reduces DNS lookup traffic and speeds up resolution for repeat visitors. Use for records that rarely change.
  • Low TTL (300 seconds / 5 minutes): Ensures changes propagate quickly. Lower your TTL before making DNS changes, then raise it again afterward.

How to Edit DNS Records in cPanel

Managing DNS records in your CyclebreezeHost account is straightforward:

  1. Log in to cPanel and navigate to the Zone Editor under the Domains section.
  2. Select the domain you want to manage.
  3. Click Add Record to create a new record, or click the Edit button next to an existing record.
  4. Choose the record type, enter the name (subdomain or root), set the TTL, and enter the value (IP address, domain name, or text content depending on the record type).
  5. Save your changes. Most records take effect within minutes, though full global propagation can take up to 24-48 hours depending on TTL settings.

Understanding DNS records gives you full control over your domain's behavior. Whether you are pointing your domain to a new server, configuring email delivery, or verifying your domain with a third-party service, the knowledge above covers the records you will encounter most frequently. If you ever need help configuring your DNS, CyclebreezeHost support is always available to assist.