Domain Setup Issues
Having trouble verifying your domain or configuring DNS records? This guide walks through the most common domain setup issues and how to resolve them.
DNS Propagation Delays
After adding DNS records at your domain registrar, it can take time for the changes to propagate across the global DNS network. This is the most common reason for verification failures.
Typical Propagation Times
- Most DNS changes: 15 minutes – 1 hour
- Full global propagation: up to 48 hours
- TTL-dependent records: check your TTL value
What to Do
- Wait at least 15 minutes before retrying verification
- Click Verify again in your dashboard after waiting
- If still failing after 1 hour, double-check your records
Common DNS Configuration Mistakes
Small errors in DNS records can prevent verification. Check for these common issues:
1. Incorrect Record Type
Ensure you are adding the correct record type. Simply Send requires specific record types for each authentication method:
| Authentication | Record Type | Purpose |
|---|---|---|
SPF | TXT | Authorizes sending infrastructure |
DKIM | CNAME | Cryptographic email signing |
DMARC | TXT | Policy enforcement for failed checks |
MAIL FROM | MX | Custom bounce handling domain |
Tracking | CNAME | Open and click tracking |
2. Extra Characters or Whitespace
When copying DNS record values from the dashboard, make sure there are no leading or trailing spaces, line breaks, or extra quotation marks. Some registrars automatically add quotes around TXT record values — if your registrar does this, do not add quotes yourself.
3. Wrong Host / Name Field
The hostname field varies by registrar. Pay attention to whether your registrar expects the full domain or just the subdomain prefix:
4. Multiple SPF Records
A domain can only have one SPF TXT record. Before adding a new SPF record, always check whether your domain already has one — for example, from Google Workspace, Microsoft 365, or another email provider. If an SPF record already exists, you must merge the Simply Send include into the existing record rather than creating a second one. Having multiple SPF records will cause all SPF checks to fail.
Check first: Run dig TXT yourdomain.com +short in your terminal or use MXToolbox SPF Lookup to see if an SPF record already exists before making changes.
5. CNAME Record with Trailing Dot
Some DNS providers require a trailing dot (.) at the end of CNAME target values to indicate a fully qualified domain name (FQDN). Others add it automatically. If verification is failing for DKIM CNAME records, try adding or removing the trailing dot.
Registrar-Specific Notes
Different domain registrars have slightly different interfaces. Here are tips for the most popular ones:
Cloudflare
- Use "DNS Only" mode (grey cloud icon) for CNAME records — do not proxy them
- Cloudflare auto-flattens CNAME records at the zone apex
- TXT records do not need quotes — Cloudflare adds them
GoDaddy
- Use the subdomain prefix only in the "Name" field (not the full domain)
- Set TTL to the minimum available (600 seconds) for faster propagation
- GoDaddy may take longer to propagate than other registrars
Namecheap
- Use the "Advanced DNS" tab to add records
- For the host field, use the subdomain only (e.g.,
_dmarc) - CNAME targets should not include a trailing dot
AWS Route 53
- Use the full domain in the name field (e.g.,
_dmarc.example.com) - Enclose TXT values in double quotes
- Route 53 propagation is typically very fast (under 60 seconds)
Verify Your DNS Records
Before retrying verification in Simply Send, you can independently confirm that your DNS records are publicly visible using these free tools:
MXToolbox
Check MX, SPF, DKIM, DMARC and more.
DNS Checker
Verify DNS propagation across global servers.
Google Dig
Google's DNS lookup tool for quick queries.
Verification Still Failing?
Pre-Check Checklist
- □DNS records match exactly what is shown in your Simply Send dashboard
- □Records are visible using an external DNS lookup tool (MXToolbox, etc.)
- □Only one SPF record exists for the domain (merged if multiple services)
- □CNAME records are not being proxied (Cloudflare: use DNS Only mode)
- □At least 15 minutes have passed since adding the records
- □No trailing spaces, extra quotes, or line breaks in record values
If you have completed all the steps above and verification still fails, our support team can help diagnose the issue. Please include your domain name and a screenshot of your DNS records when contacting us.
Contact Support