Documentation

Domain Authentication

Required
DNS Setup

Authenticate your domain with DNS records to ensure your emails are trusted by recipients and email providers. This is required before sending any emails through Laneful.

Required Step

Cannot send emails without this

One-Time Setup

Set it up once, use forever

Essential
Security

Why Domain Authentication is Required

Domain authentication proves to email providers (Gmail, Outlook, etc.) that you legitimately own the domain you're sending emails from. Without it, your emails will be rejected or marked as spam.

What Domain Authentication Provides

Security

  • • Prevents domain spoofing
  • • Protects against phishing
  • • Verifies sender identity

Deliverability

  • • Improves inbox placement
  • • Reduces spam filtering
  • • Builds sender reputation

What DNS Records to Add

Laneful will provide you with specific DNS records to add to your domain. Here's what each record does:

When you add a domain (e.g., yourdomain.com) in Laneful, you'll need to add these specific DNS records. Replace "yourdomain.com" in the examples below with your actual domain.

Required DNS Records

TypeHostValuePurpose
CNAMEbounces.yourdomain.comrp.laneful.netBounce handling
CNAMEclick.yourdomain.comtrack.laneful.netClick tracking
CNAMEdkim1._domainkey.yourdomain.comdkim1._domainkey.laneful.netDKIM signature 1
CNAMEdkim2._domainkey.yourdomain.comdkim2._domainkey.laneful.netDKIM signature 2
TXT_dmarc.yourdomain.comv=DMARC1;p=none;rua=mailto:dmarc@rp.laneful.net;DMARC policy

Bounce & Click Tracking CNAMEs

These CNAME records enable bounce handling and click tracking using your custom domain.

Bounce Handling

bounces.yourdomain.com → rp.laneful.net

Click Tracking

click.yourdomain.com → track.laneful.net

DKIM Authentication CNAMEs

Dual DKIM records provide cryptographic signatures to verify email authenticity.

DKIM Key 1

dkim1._domainkey.yourdomain.com → dkim1._domainkey.laneful.net

DKIM Key 2

dkim2._domainkey.yourdomain.com → dkim2._domainkey.laneful.net

DMARC Policy Record (TXT)

DMARC policy tells email providers how to handle emails that fail authentication.

_dmarc.yourdomain.com → v=DMARC1;p=none;rua=mailto:dmarc@rp.laneful.net;
Note: The policy starts with p=none (monitoring only). Laneful will help you transition to stricter policies as your domain builds reputation.

Step-by-Step Setup Guide

1

Add Your Domain in Laneful

In your Laneful dashboard, go to Workspace Settings → Manage Domains and click "Add Domain". Enter the domain you want to send emails from (e.g., company.com).

Dashboard → Workspace Settings → Manage Domains → Add Domain
2

Copy the DNS Records

Laneful will generate unique DNS records for your domain. Copy each record exactly as shown. Click the copy button to avoid typos.

Important: Each domain gets unique records. Don't reuse records from other domains.
3

Add Records to Your DNS Provider

Log into your DNS provider (where you manage your domain's DNS settings) and add each TXT record. Common providers include:

Cloudflare
Namecheap
GoDaddy
Route 53
4

Wait for DNS Propagation

DNS changes can take 5 minutes to 24 hours to propagate globally. Most changes are visible within 15-30 minutes.

Tip: You can check DNS propagation using tools like whatsmydns.net
5

Verify in Laneful

Return to Workspace Settings → Manage Domains and click "Verify Domain". Laneful will check all 5 DNS records and mark your domain as verified when complete.

Success: Once all records are verified, you can start sending emails from this domain!

Verification Process

Understanding what happens during domain verification helps troubleshoot any issues.

What Laneful Checks

Bounce handling CNAME (bounces.yourdomain.com)
Click tracking CNAME (click.yourdomain.com)
DKIM key 1 CNAME (dkim1._domainkey.yourdomain.com)
DKIM key 2 CNAME (dkim2._domainkey.yourdomain.com)
DMARC policy TXT record (_dmarc.yourdomain.com)

Verification Status Indicators

Verified: Domain is ready for sending
Pending: DNS records not yet propagated
Failed: DNS records missing or incorrect

Troubleshooting

Common issues and solutions when setting up domain authentication.

"DNS Records Not Found"

Possible causes:

  • • DNS changes haven't propagated yet (wait 30 minutes)
  • • Records added to wrong domain or subdomain
  • • Typo in the DNS record values
  • • Using wrong record type (should be TXT)

Solutions:

  • • Double-check the record name and value
  • • Use a DNS lookup tool to verify the records exist
  • • Contact your DNS provider if records aren't appearing

"SPF Record Already Exists"

What this means:

Your domain already has an SPF record. You need to modify it to include Laneful.

Solution:

Instead of creating a new SPF record, modify your existing one to include:

include:_spf.laneful.com

Example: v=spf1 include:_spf.google.com include:_spf.laneful.com ~all

"Verification Taking Too Long"

Normal timeframes:

  • • Most DNS changes: 5-30 minutes
  • • Some providers: up to 2 hours
  • • Maximum: 24-48 hours

To check progress:

  • • Use nslookup or dig commands
  • • Check whatsmydns.net for global propagation
  • • Try the "Verify Domain" button periodically

Still Need Help?

If you're still having issues after trying these solutions: