Sender Domain DNS Settings
Proper DNS configuration for your sender domains is essential for email deliverability. Without correct DNS records, your emails may be marked as spam or rejected entirely by recipient mail servers.
Required DNS Records
For each sender domain you use in Octeth, you need to configure three types of DNS records:
- SPF (Sender Policy Framework) - Authorizes which servers can send email from your domain
- DKIM (DomainKeys Identified Mail) - Cryptographically signs your emails to verify authenticity
- DMARC (Domain-based Message Authentication, Reporting & Conformance) - Tells receiving servers how to handle authentication failures
Get Your DNS Records from Octeth
Octeth automatically generates the correct DNS records for each sender domain.
Access Sender Domain Settings
- Log in to Octeth Admin Dashboard
- Navigate to Settings > Sender Domains
- Click on your sender domain (or create a new one)
- View the DNS Configuration section
Octeth will display the exact DNS records you need to add to your domain's DNS management panel.
DNS Record Examples
Here's what the DNS records typically look like (your actual values will be different):
SPF Record
Type: TXT Name: @ or your domain Value:
v=spf1 include:_spf.example.com ~allThe SPF record authorizes Octeth's servers to send email on behalf of your domain.
DKIM Record
Type: TXT Name: octeth._domainkey (or custom selector from Octeth) Value:
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC...The DKIM record contains the public key that receiving servers use to verify your email signatures.
DKIM Key Length
The DKIM value will be a very long string (often 300+ characters). Make sure your DNS provider accepts long TXT records. If they have a character limit, you may need to upgrade your DNS service or contact support.
DMARC Record
Type: TXT Name: _dmarcValue:
v=DMARC1; p=quarantine; rua=mailto:admin@example.com; ruf=mailto:admin@example.com; pct=100The DMARC record tells receiving servers what to do if SPF or DKIM validation fails.
DMARC Policies:
p=none- Monitor only (recommended for testing)p=quarantine- Send suspicious emails to spamp=reject- Reject emails that fail authentication (strictest)
Adding DNS Records
The process varies by DNS provider, but generally:
Step 1: Access DNS Management
Log in to your domain registrar or DNS hosting provider (e.g., Cloudflare, GoDaddy, Namecheap, Route53).
Step 2: Add TXT Records
For each DNS record provided by Octeth:
- Click "Add Record" or "Add DNS Record"
- Select TXT as the record type
- Enter the Name (host) exactly as shown
- Paste the Value exactly as provided by Octeth
- Set TTL to 3600 (1 hour) or use automatic
- Save the record
Step 3: Wait for DNS Propagation
DNS changes can take anywhere from a few minutes to 48 hours to propagate worldwide. Typically, changes are visible within 1-4 hours.
Verify DNS Records
After adding the records, verify they're configured correctly.
Using Octeth's Built-in Verification
- In Octeth Admin > Settings > Sender Domains
- Click Verify DNS next to your domain
- Octeth will check all required records
- Fix any issues reported
Using Command Line Tools
You can also manually verify using command-line tools:
Check SPF:
dig TXT yourdomain.com +shortCheck DKIM:
dig TXT octeth._domainkey.yourdomain.com +shortCheck DMARC:
dig TXT _dmarc.yourdomain.com +shortReplace yourdomain.com with your actual domain.
Using Online Tools
Several free online tools can verify your DNS configuration:
- MXToolbox - SPF and DKIM checker
- DMARC Analyzer - DMARC validation
- Google Admin Toolbox - Complete email DNS check
Common Issues and Solutions
SPF Record Not Found
Problem: DNS lookup shows no SPF record Solution:
- Verify you added a TXT record, not an SPF record type
- Check the record name is
@or your bare domain - Wait for DNS propagation (can take up to 24 hours)
DKIM Record Too Long
Problem: DNS provider rejects the DKIM record Solution:
- Some DNS providers have TXT record length limits
- Contact your DNS provider support for assistance
- Consider switching to a provider that supports long TXT records (Cloudflare, Route53)
Multiple SPF Records
Problem: You already have an SPF record for another email service Solution:
- You can only have ONE SPF record per domain
- Merge the records by combining include statements:
v=spf1 include:_spf.google.com include:_spf.octeth.com ~allDMARC Policy Too Strict
Problem: Legitimate emails are being rejected Solution:
- Start with
p=noneto monitor without affecting delivery - Review DMARC reports sent to the
ruaemail address - Gradually tighten policy after verifying configuration
Best Practices
Start with Monitoring
- Begin with DMARC policy
p=noneto collect data - Review reports for 2-4 weeks before tightening policy
- Gradually move to
p=quarantinethenp=reject
Use Subdomains for Campaigns
- Use
mail.yourdomain.comfor marketing emails - Keep
yourdomain.comfor transactional emails - This protects your main domain reputation
Monitor DNS Health
- Set up monitoring alerts for DNS record changes
- Regularly verify records are still correctly configured
- Check DMARC reports weekly for authentication issues
Keep Records Updated
- If you change email infrastructure, update DNS records
- When rotating DKIM keys, update the DNS record
- Document all DNS changes for your team
Next Steps
Once your DNS records are properly configured and verified:
- Test email delivery by sending test campaigns
- Monitor delivery rates and spam reports
- Set up Monitoring to track system health
- Review Troubleshooting if you encounter issues
Professional Help
If you're unsure about DNS configuration, consider hiring a professional or contacting Octeth support for assistance. Incorrect DNS settings can seriously impact email deliverability.

Help Portal