Custom Email Domain DNS Setup
Step-by-step DNS configuration for custom email sending domains.
Using a custom sending domain improves email deliverability, reinforces your brand in customer inboxes, and ensures SPF/DKIM alignment. This guide walks you through adding the required DNS records for your domain.
Why Custom Domains Matter
When LostChurn sends dunning emails on your behalf, the "From" address domain affects whether emails land in the inbox or spam folder:
| Sending Method | From Address | Deliverability | Brand Trust |
|---|---|---|---|
| LostChurn subdomain | billing@yourco.send.lostchurn.com | Good | Low -- unfamiliar domain |
| Custom domain | billing@yourcompany.com | Excellent | High -- your own domain |
Custom domains provide:
- SPF alignment -- the sending IP is authorized by your domain's SPF record
- DKIM signing -- emails are cryptographically signed with your domain's key
- DMARC compliance -- SPF + DKIM alignment satisfies DMARC policies
- Brand recognition -- customers see your domain, not a third-party subdomain
Prerequisites
Before starting, you need:
- Access to your domain's DNS management panel
- The DNS records from LostChurn (found in Settings → Email → Custom Domain)
- About 10 minutes for configuration (plus propagation time)
Getting Your DNS Records
- Go to Settings → Email → Custom Domain
- Enter the domain you want to send from (e.g.,
billing.yourcompany.com) - Click Generate Records
- LostChurn displays the DNS records you need to add
You will need to add three types of records:
| Record Type | Purpose | Name Example | Value Example |
|---|---|---|---|
| CNAME | Email sending delegation | billing.yourcompany.com | send.lostchurn.com |
| TXT | SPF authorization | billing.yourcompany.com | v=spf1 include:spf.lostchurn.com ~all |
| CNAME | DKIM signing | lc._domainkey.billing.yourcompany.com | dkim.lostchurn.com |
The exact record values are unique to your account. Always copy them from the LostChurn settings page rather than using the examples above.
Provider-Specific Instructions
Cloudflare
- Log in to the Cloudflare Dashboard
- Select your domain
- Go to DNS → Records
- Click Add Record for each record:
CNAME record (sending delegation):
Type: CNAME
Name: billing (or your chosen subdomain)
Target: send.lostchurn.com
Proxy: DNS only (grey cloud -- important!)
TTL: AutoTXT record (SPF):
Type: TXT
Name: billing (or your chosen subdomain)
Content: v=spf1 include:spf.lostchurn.com ~all
TTL: AutoCNAME record (DKIM):
Type: CNAME
Name: lc._domainkey.billing
Target: dkim.lostchurn.com
Proxy: DNS only (grey cloud)
TTL: AutoFor Cloudflare, make sure the CNAME records use DNS only mode (grey cloud icon), not Proxied (orange cloud). Proxied CNAME records will break email sending delegation.
AWS Route 53
- Open the Route 53 Console
- Go to Hosted Zones → select your domain
- Click Create Record for each:
CNAME record (sending delegation):
Record name: billing.yourcompany.com
Record type: CNAME
Value: send.lostchurn.com
TTL: 300
Routing: Simple routingTXT record (SPF):
Record name: billing.yourcompany.com
Record type: TXT
Value: "v=spf1 include:spf.lostchurn.com ~all"
TTL: 300CNAME record (DKIM):
Record name: lc._domainkey.billing.yourcompany.com
Record type: CNAME
Value: dkim.lostchurn.com
TTL: 300In Route 53, TXT record values must be enclosed in double quotes. CNAME values do not need quotes.
GoDaddy
- Log in to your GoDaddy Account
- Go to My Products → select your domain → DNS Management
- Click Add under the DNS Records section for each record:
CNAME record (sending delegation):
Type: CNAME
Name: billing
Value: send.lostchurn.com
TTL: 1 HourTXT record (SPF):
Type: TXT
Name: billing
Value: v=spf1 include:spf.lostchurn.com ~all
TTL: 1 HourCNAME record (DKIM):
Type: CNAME
Name: lc._domainkey.billing
Value: dkim.lostchurn.com
TTL: 1 HourNamecheap
- Log in to Namecheap
- Go to Domain List → select your domain → Advanced DNS
- Under Host Records, click Add New Record for each:
CNAME record (sending delegation):
Type: CNAME Record
Host: billing
Value: send.lostchurn.com
TTL: AutomaticTXT record (SPF):
Type: TXT Record
Host: billing
Value: v=spf1 include:spf.lostchurn.com ~all
TTL: AutomaticCNAME record (DKIM):
Type: CNAME Record
Host: lc._domainkey.billing
Value: dkim.lostchurn.com
TTL: AutomaticGoogle Domains
- Go to Google Domains
- Select your domain → DNS → Custom Records
- Click Manage Custom Records and add each record:
CNAME record (sending delegation):
Host name: billing
Type: CNAME
TTL: 3600
Data: send.lostchurn.comTXT record (SPF):
Host name: billing
Type: TXT
TTL: 3600
Data: v=spf1 include:spf.lostchurn.com ~allCNAME record (DKIM):
Host name: lc._domainkey.billing
Type: CNAME
TTL: 3600
Data: dkim.lostchurn.comVercel
- Go to your Vercel Dashboard
- Select your project → Settings → Domains
- Select your domain → DNS Records
- Click Add for each record:
CNAME record (sending delegation):
Type: CNAME
Name: billing
Value: send.lostchurn.comTXT record (SPF):
Type: TXT
Name: billing
Value: v=spf1 include:spf.lostchurn.com ~allCNAME record (DKIM):
Type: CNAME
Name: lc._domainkey.billing
Value: dkim.lostchurn.comVerification Process
After adding all DNS records, return to LostChurn to verify:
- Go to Settings → Email → Custom Domain
- Click Verify DNS Records
- LostChurn checks each record and displays the status
Verification Statuses
| Status | Meaning | Action |
|---|---|---|
| Verified | Record found and correct | No action needed |
| Pending | Record not yet detected | Wait for DNS propagation |
| Mismatch | Record found but value is incorrect | Update the record value |
| Missing | Record not found at all | Add the record to your DNS |
Verification checks run automatically every 15 minutes. You can also click Verify to trigger an immediate check.
Troubleshooting DNS Propagation
DNS changes do not take effect instantly. Propagation time depends on your provider and TTL settings.
Expected Propagation Times
| Provider | Typical Time | Maximum Time |
|---|---|---|
| Cloudflare | Instant - 5 minutes | 5 minutes |
| AWS Route 53 | 1 - 10 minutes | 60 minutes |
| GoDaddy | 10 - 30 minutes | 48 hours |
| Namecheap | 10 - 30 minutes | 48 hours |
| Google Domains | 5 - 15 minutes | 48 hours |
| Vercel | 1 - 5 minutes | 30 minutes |
Common Issues
Records not detected after 48 hours:
- Verify you added the records to the correct domain (not a subdomain or different zone)
- Check for typos in the record name and value
- Ensure you saved the changes in your DNS provider's panel
CNAME conflict with existing records:
- A CNAME record cannot coexist with other record types on the same name
- If you have an existing A or AAAA record on
billing.yourcompany.com, remove it before adding the CNAME
SPF "too many lookups" error:
- SPF allows a maximum of 10 DNS lookups
- If your existing SPF record already has many
include:entries, you may need to consolidate - Consider using an SPF flattening service if you are at the limit
DKIM verification failing:
- Ensure the DKIM CNAME name is exactly
lc._domainkey.billing(with your subdomain) - Some providers add the root domain automatically -- enter only the subdomain portion
Checking DNS Records Manually
You can verify your records have propagated using command-line tools:
# Check CNAME record
dig billing.yourcompany.com CNAME +short
# Check TXT record (SPF)
dig billing.yourcompany.com TXT +short
# Check DKIM CNAME
dig lc._domainkey.billing.yourcompany.com CNAME +shortOr use an online tool like DNS Checker to see propagation status across global DNS servers.
Auto-Provision Alternative
If you prefer not to configure DNS, you can use LostChurn's auto-provisioned subdomain:
yourcompany.send.lostchurn.comThis requires zero DNS setup and is available immediately. To use the auto-provisioned domain:
- Go to Settings → Email → Custom Domain
- Click Use LostChurn Subdomain
- Enter your preferred prefix (typically your company name)
- The domain is active immediately -- no verification needed
The auto-provisioned subdomain includes LostChurn's SPF and DKIM configuration automatically. Deliverability is good but may be slightly lower than a custom domain because recipient mail servers see a third-party domain.
You can switch from the auto-provisioned domain to a custom domain at any time without disrupting active recoveries. Emails already queued will be sent from the old domain; new emails will use the updated domain.
Next Steps
- Quick Setup Wizard -- configure email as part of the guided setup
- Email Templates -- customize dunning email content and design
- Security -- learn about email encryption and data protection