All topics
English

Email marketing · 3 min read

Authenticate the domain with DNS records

Publish correct values, interpret checks and preserve existing email service.

In this guide
  1. Understand the requested records
  2. Copy and publish without duplicating the name
  3. Preserve existing receiving and policy
  4. Verify and interpret results
  5. Related guides

For Insurance agency Owners and administrators.

Understand the requested records

In DNS authentication, check Selected domain and the verified-record count. Expand a row for Type, Relative name, DNS value and Full hostname. Use values generated for your agency, not the demonstration images.

RecordPractical role
DKIM signature — CNAMESupports validation of signed domain messages. Publish each requested selector.
Message return path — MXDefines technical return handling on the indicated subdomain. It does not replace the main domain’s incoming-mail MX.
SPF authorization — TXTDeclares sending authorization at the specified hostname.
DMARC policy — TXTDefines authentication policy. Preserve an existing recognized policy.
Fictitious records with different states: check the selected domain and each result.
Fictitious records with different states: check the selected domain and each result. Open the image to enlarge it.

Copy and publish without duplicating the name

  1. Open the DNS manager responsible for the correct domain zone. If unavailable to you, send instructions to its administrator.
  2. Copy the type and values using CRMDAY’s corresponding buttons.
  3. If the provider appends the domain, use Relative name; if it requires the full name, use Full hostname. Avoid name.youragency.com.youragency.com.
  4. For CNAME, check name and destination. On Cloudflare, keep authentication records DNS only, without proxying.
  5. For MX, put priority in its separate field and omit that number from the destination. For TXT, paste without adding quotation marks.
  6. Expand DNS provider help, select the provider where applicable and download instructions when needed.

The DKIM image shows a fictitious difference between expected and observed values. Compare before editing. The workspace does not publish DNS automatically. See Cloudflare’s official record-field documentation.

Demonstration DKIM detail with relative name, full hostname, expected value and fictitious mismatch.
Demonstration DKIM detail with relative name, full hostname, expected value and fictitious mismatch. Open the image to enlarge it.

Preserve existing receiving and policy

The return-path MX belongs to the displayed hostname, usually a return subdomain. Do not remove MX records used by agency inboxes. Relative name mail and priority 10 in the image are examples; use your screen’s generated name and priority.

If DMARC is Verified, keep the recognized policy. Do not publish duplicate DMARC or replace a stronger policy with p=none merely to copy a suggestion. For conflicting SPF or other records at the same hostname, request technical review instead of adding duplicates. See the delivery service’s official MAIL FROM documentation.

Fictitious return-path MX: separate priority and indicated subdomain hostname. Do not copy these values.
Fictitious return-path MX: separate priority and indicated subdomain hostname. Do not copy these values. Open the image to enlarge it.

Verify and interpret results

  1. After publishing, return to the correct CRMDAY domain.
  2. Use the row verification button or Check all records.
  3. Review states and expand for observed values and check time.
  4. Correct indicated issues, allow propagation and verify again.
  5. Continue to Sender; it can be prepared while authentication finishes.
StateAction
Not checkedA check is still needed.
Not foundCheck publication, hostname, zone and propagation.
Value mismatchCompare expected, observed and duplicate records.
Lookup unavailableRetry later; lookup failure does not require DNS edits.
VerifiedThe record is recognized; preserve valid values.

Help mentions propagation up to 72 hours as guidance, not a guaranteed deadline. If records are correct but the delivery service has not confirmed, wait and verify again. Valid DNS does not remove an account block, exhausted allowance or pause.

Related guides

Updated October 25, 2026.