Waymaker
Email

DNS Records

DNS records tell the internet how to handle your domain's email. WaymakerOS requires several records for proper email delivery:

DNSTechnical
Last updated: February 2026

This guide explains the DNS records required to send email from your domain through WaymakerOS.

Overview

DNS records tell the internet how to handle your domain's email. WaymakerOS requires several records for proper email delivery:

  • MX records - Where to deliver incoming email
  • SPF record - Who can send email for your domain
  • DKIM records - Cryptographic signatures for your emails
  • DMARC record - Your email authentication policy

Required Records

When you add a domain in WaymakerOS, you'll see the exact values to use. Here's what each record type does:

MX Records (Mail Exchange)

MX records tell other mail servers where to deliver email for your domain.

TypeHostValuePriority
MX@mail.waymakerone.com10

Notes:

  • The "@" symbol means your root domain
  • Priority 10 is standard for a single mail server
  • This redirects ALL email for your domain to WaymakerOS

SPF Record (Sender Policy Framework)

SPF tells receiving servers which servers are allowed to send email for your domain.

TypeHostValue
TXT@v=spf1 include:spf.waymakerone.com ~all

Notes:

  • Must be a TXT record
  • If you have an existing SPF record, add include:spf.waymakerone.com to it
  • Only one SPF record per domain is allowed

DKIM Records (DomainKeys Identified Mail)

DKIM adds a cryptographic signature to your emails, proving they're really from you.

TypeHostValue
CNAMEwm1._domainkeywm1.dkim.waymakerone.com
CNAMEwm2._domainkeywm2.dkim.waymakerone.com

Notes:

  • Two DKIM records for redundancy
  • The host values include "._domainkey" suffix
  • These are CNAME records, not TXT

DMARC Record

DMARC tells receivers what to do if SPF or DKIM fails.

TypeHostValue
TXT_dmarcv=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

Notes:

  • Start with p=quarantine or p=none while testing
  • Change to p=reject once everything works
  • The rua address receives DMARC reports

Adding Records by Registrar

GoDaddy

  1. Sign in to your GoDaddy account
  2. Go to My Products > Domains
  3. Select your domain and click DNS
  4. Click Add to create each record
  5. Select the record type and enter values
  6. Save and wait for propagation

Cloudflare

  1. Sign in to Cloudflare
  2. Select your domain
  3. Go to DNS > Records
  4. Click Add record
  5. Select type, enter name and value
  6. Click Save

Cloudflare propagates quickly, usually within minutes.

Namecheap

  1. Sign in to Namecheap
  2. Go to Domain List > Manage
  3. Click Advanced DNS
  4. Click Add New Record
  5. Select type and enter values
  6. Save changes

Google Domains / Squarespace Domains

  1. Sign in to your Google/Squarespace account
  2. Go to Domains > DNS
  3. Scroll to Custom records
  4. Add each record with type and values
  5. Save

Other Registrars

The process is similar for all registrars:

  1. Find DNS settings or DNS management
  2. Look for "Add Record" or similar
  3. Select the record type
  4. Enter the host/name and value
  5. Save and wait for propagation

Common Issues

Existing SPF Record

If you already have an SPF record, don't create a second one. Instead, modify the existing record:

Before: v=spf1 include:_spf.google.com ~all

After: v=spf1 include:_spf.google.com include:spf.waymakerone.com ~all

TTL (Time to Live)

TTL controls how long DNS records are cached:

  • Lower TTL (300 seconds) = Faster propagation, more DNS lookups
  • Higher TTL (3600+ seconds) = Slower propagation, fewer lookups

During setup, use a low TTL. After verification, you can increase it.

Record Already Exists

If you see an error about duplicate records:

  1. Check for existing records of the same type and host
  2. Update or remove the conflicting record
  3. Add the new record

Propagation Time

DNS changes aren't instant:

  • Cloudflare: Usually under 5 minutes
  • Most registrars: 15-30 minutes
  • Some providers: Up to 48 hours

If verification fails, wait and try again.

Verifying Your Records

Use these tools to check your DNS configuration:

Security Recommendations

Start with Quarantine

Set DMARC to p=quarantine initially. This sends suspicious emails to spam rather than rejecting them. Once you're confident everything works, change to p=reject.

Monitor DMARC Reports

Set up a rua email address to receive DMARC reports. These show who's sending email as your domain and whether it's passing authentication.

Keep Records Updated

If you change email providers, update your SPF record. Having multiple include: statements for old providers can cause issues.

Frequently Asked Questions

Do I need all these records?

MX and SPF are required. DKIM and DMARC are highly recommended for deliverability and security.

Can I keep my old email provider during transition?

Not for the same domain. MX records can only point to one destination. Use a subdomain or complete your migration before switching.

What's the "host" or "name" field?

This is the subdomain or record name. Use "@" or leave blank for the root domain. Use "_dmarc" for DMARC, etc.

Why are my emails going to spam?

Missing or incorrect DKIM/DMARC records often cause this. Verify all records are in place and check your DMARC reports.