DNS (Domain Name System) records are the instructions that tell the internet how to find and connect to your website, email server, and other online services. Understanding DNS records is essential for managing your domain effectively, troubleshooting connectivity issues, and configuring third-party services. This guide explains every major DNS record type you will encounter as a SakuraHost user.

Manage Your DNS: You can manage DNS records in cPanel under Domains → Zone Editor, or through the SakuraHost client area at billing.sakurahost.co.tz.

How DNS Works: A Quick Overview

When someone types your domain name (e.g., yourdomain.co.tz) into their browser, their computer queries DNS servers to find the IP address associated with that domain. This process is called DNS resolution. The DNS servers consult your domain's zone file, which contains various records that map domain names to IP addresses, mail servers, and other destinations.

Think of DNS as the internet's phone book. Your domain name is the contact name, and the DNS records are the phone numbers and addresses associated with that name.

A Record (Address Record)

The A record is the most fundamental DNS record. It maps a domain name to an IPv4 address, telling browsers which server hosts your website.

Type: A
Name: yourdomain.co.tz
Value: 5.252.55.145
TTL: 14400

You can have multiple A records for the same domain (for load balancing or failover). The Name field can be the root domain (@) or a subdomain (blog for blog.yourdomain.co.tz). The Value is always an IPv4 address in dotted decimal format.

AAAA Record (IPv6 Address Record)

The AAAA record is the IPv6 equivalent of the A record. It maps a domain name to an IPv6 address. As IPv6 adoption grows, having AAAA records ensures your website is accessible to visitors using IPv6 connectivity.

Type: AAAA
Name: yourdomain.co.tz
Value: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
TTL: 14400

CNAME Record (Canonical Name Record)

A CNAME record creates an alias that points one domain name to another domain name (not an IP address). This is commonly used for subdomains and third-party service integrations.

Type: CNAME
Name: www
Value: yourdomain.co.tz
TTL: 14400

In this example, www.yourdomain.co.tz points to yourdomain.co.tz, which in turn resolves via its A record to the server's IP address. Common uses for CNAME records include:

  • Pointing www to the root domain
  • Configuring custom domains for services like Google Workspace verification, Shopify, or Mailchimp landing pages
  • Setting up subdomains for CDN services like Cloudflare
Important Rule: A CNAME record cannot coexist with any other record type for the same name. You cannot have a CNAME and an MX record, or a CNAME and a TXT record, for the same subdomain. Additionally, you should never place a CNAME record on the root domain (@) as it can break email and other services.

MX Record (Mail Exchange Record)

MX records specify which mail servers are responsible for receiving email for your domain. Without correctly configured MX records, email sent to your domain will not be delivered.

Type: MX
Name: yourdomain.co.tz
Priority: 0
Value: mail.yourdomain.co.tz
TTL: 14400

The Priority value (also called preference) determines the order in which mail servers are tried. Lower numbers have higher priority. If you have multiple MX records, email is delivered to the lowest-priority server first, with higher-priority servers serving as fallbacks.

If you use external email services, you will need to replace the default MX records with those provided by your email provider:

# Google Workspace MX Records
Priority 1   ASPMX.L.GOOGLE.COM
Priority 5   ALT1.ASPMX.L.GOOGLE.COM
Priority 5   ALT2.ASPMX.L.GOOGLE.COM
Priority 10  ALT3.ASPMX.L.GOOGLE.COM
Priority 10  ALT4.ASPMX.L.GOOGLE.COM

TXT Record (Text Record)

TXT records store arbitrary text data associated with your domain. They serve many purposes in modern DNS, with the most important being email authentication and domain verification.

SPF (Sender Policy Framework)

SPF records specify which servers are authorized to send email on behalf of your domain. This helps prevent email spoofing and improves email deliverability.

Type: TXT
Name: yourdomain.co.tz
Value: v=spf1 +a +mx +ip4:5.252.55.145 ~all
TTL: 14400

This SPF record authorizes the server at the A record, the MX server, and the specific IP address to send email for the domain. The ~all softfails all other senders.

DKIM (DomainKeys Identified Mail)

DKIM adds a digital signature to outgoing emails, allowing receiving servers to verify the email was genuinely sent from your domain and was not tampered with in transit. DKIM records are TXT records with a specific naming format:

Type: TXT
Name: default._domainkey
Value: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBA...(public key)

DMARC (Domain-based Message Authentication)

DMARC builds on SPF and DKIM to provide policy instructions for handling emails that fail authentication checks.

Type: TXT
Name: _dmarc
Value: v=DMARC1; p=quarantine; rua=mailto:admin@yourdomain.co.tz

Domain Verification

Many third-party services (Google Search Console, Microsoft 365, Facebook Business) require you to add a TXT record to verify domain ownership.

SRV Record (Service Record)

SRV records define the location (hostname and port) of specific services. They are used by protocols like SIP, XMPP, and Microsoft 365 services (Skype for Business, Teams).

Type: SRV
Name: _sip._tcp.yourdomain.co.tz
Priority: 10
Weight: 60
Port: 5060
Target: sipserver.yourdomain.co.tz

CAA Record (Certification Authority Authorization)

CAA records specify which certificate authorities are allowed to issue SSL certificates for your domain. This provides an additional layer of security against unauthorized certificate issuance.

Type: CAA
Name: yourdomain.co.tz
Value: 0 issue "sectigo.com"
TTL: 14400

TTL (Time to Live)

Every DNS record has a TTL value measured in seconds. TTL controls how long DNS resolvers cache the record before checking for updates. Common TTL values are 300 (5 minutes), 3600 (1 hour), and 14400 (4 hours). Lower TTLs mean changes propagate faster but generate more DNS queries. For more about how DNS changes propagate, see our article on Understanding DNS Propagation and Why Changes Take Time.

Before Making DNS Changes: Lower your TTL to 300 seconds (5 minutes) at least 24 hours before making important DNS changes. This ensures the old, higher TTL expires from caches, and your new changes will propagate quickly.

For comprehensive DNS documentation, visit Cloudflare's DNS Learning Center or the cPanel Zone Editor documentation. For assistance managing your DNS records, contact SakuraHost support at billing.sakurahost.co.tz.

Was this answer helpful? 0 Users Found This Useful (0 Votes)