Skip to content
English
  • There are no suggestions because the search field is empty.

Understanding DNS Record Types and Names for Email deliverability configuration.

DNS Records for Email Authentication (Works for GoDaddy and Other Domain Providers)

This article explains the DNS record types you’ll use to authenticate email sending and improve deliverability. While the examples reference GoDaddy-style fields, the same records apply to any DNS host (Cloudflare, Namecheap, Google Domains/Squarespace Domains, Network Solutions, Hover, etc.). The only difference is what your provider labels the fields (for example, Host/Name vs Record name).

On this Page

What commonsku provides vs what you may see in your email platform

commonsku only provides the following DNS entries for your domain updates:

  • SPF (TXT record)

  • CNAME record(s)

We do not provide a DKIM record directly.
In most setups, DKIM is handled by your email sending service via CNAME records. If the SPF TXT and the CNAME record(s) you add match what commonsku provides, then DKIM should authenticate correctly once DNS propagates.

DMARC is optional but recommended. It’s a separate TXT record you can add to control policy and reporting.

DNS fields across providers (GoDaddy vs others)

Most DNS providers ask for the same information:

  • Type: TXT, CNAME, A, etc.

  • Name / Host: what comes before your domain

  • Value / Content / Target: what the record points to (or the text value)

  • TTL: cache time (defaults are fine)

How “Name/Host” works

  • @ means the root domain (example.com)

  • www means www.example.com

  • _dmarc means _dmarc.example.com

  • selector._domainkey means selector._domainkey.example.com

CNAME records are commonly used for verification and DKIM enablement. The most frequent issue is that different DNS providers expect the Name/Host field differently—especially for DKIM-style records that include _domainkey (sometimes written or misread as “domainKey”).

The key rule

Your goal is that the final record name becomes:

  • selector1._domainkey.yourdomain.com

But different DNS providers want you to type different things in the Name/Host box to achieve that.

Common DNS record types

A Record

Maps a name to an IPv4 address (often for your website).

  • Type: A

  • Name/Host: @ or a subdomain like www

  • Value: an IP address

CNAME Record

Points a hostname to another hostname (common for verification and email auth).

  • Type: CNAME

  • Name/Host: a subdomain/label (e.g., tracking, selector1._domainkey)

  • Value/Target: another hostname provided by the service

TXT Record

Stores text values (SPF, DMARC, verification tokens).

  • Type: TXT

  • Name/Host: @ or a label like _dmarc

  • Value/Content: text string

SPF (TXT record)

What SPF does

SPF tells receiving mail servers which services are allowed to send email from your domain, reducing spoofing and improving deliverability.

Important SPF rules

  • You should only have one SPF record per hostname (usually one TXT at @ containing one v=spf1 ... string).

  • If you use multiple senders (e.g., Microsoft 365 + another platform), you combine includes into a single SPF value.

  • SPF has a DNS lookup limit (10). Too many include: entries can cause SPF to fail.

How to add SPF (any provider)

Create or edit a TXT record:

  • Type: TXT

  • Name/Host: @

  • Value: provided SPF string (from commonsku)

Example format:

  • v=spf1 include:example-sender.com ~all

~all vs -all

  • ~all (soft fail): safer while validating setup

  • -all (hard fail): stricter, use once confident you’ve included every legitimate sender

CNAME records (commonly used for verification and DKIM enablement)

Why CNAMEs matter here

Many email systems “enable DKIM” by having you publish CNAME records that point to their DKIM keys. You may not be adding a TXT key directly; instead, the provider checks the CNAME(s) and uses them to validate DKIM.

How to add CNAMEs (any provider)

Create one or more CNAME records exactly as provided:

  • Type: CNAME

  • Name/Host: (example) selector1._domainkey

  • Value/Target: (example) selector1.something.provider.com

commonsku will provide the CNAME record(s) needed. If those match exactly, DKIM should validate once DNS propagates.

DKIM (what you need to know)

What DKIM does

DKIM digitally signs outbound email so recipients can verify the message is authentic and unaltered.

Key point for commonsku users

  • commonsku does not provide a DKIM TXT record.

  • DKIM is typically verified/activated through the CNAME record(s) commonsku provides.

  • If the SPF TXT and CNAME record(s) are correct, DKIM should update/align correctly on its own after propagation.

DMARC (recommended)

What DMARC does

DMARC tells receiving servers what to do when SPF/DKIM fail and provides reporting so you can monitor authentication and spoofing attempts.

DMARC record basics

DMARC is a TXT record at:

  • Type: TXT

  • Name/Host: _dmarc

  • Value: policy string

Suggested DMARC rollout

Start in monitor-only mode, then tighten:

Monitoring:

  • v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; adkim=s; aspf=s; pct=100

Stronger enforcement (later):

  • p=quarantine or p=reject

Use a dedicated mailbox for rua= (reports can be noisy), or a DMARC reporting service.

Quick checklist (any DNS provider)

  1. Add/confirm SPF (TXT at @) exactly as provided by commonsku

  2. Add/confirm CNAME record(s) exactly as provided by commonsku

  3. (Optional but recommended) Add DMARC (TXT at _dmarc)

  4. Wait for DNS propagation (can be minutes to 24–48 hours depending on TTL/provider)

  5. Re-check authentication status in your sending platform/tools

Quick Reference: What to Enter in the email domain host. 

Purpose Type Name/Host Value (example)
WWW alias CNAME www example.host.com
SPF TXT @ v=spf1 include:_spf.google.com ~all