Domain Setup
Domain Setup
This guide covers DNS configuration. See the full Setup Checklist to verify all steps for production readiness.
To send and receive emails with Postscale, you need to configure your domain's DNS records. This guide walks you through the complete setup process.
Adding a Domain
- Log in to the Postscale Dashboard
- Navigate to Domains → Add Domain
- Enter your domain name (e.g.,
yourcompany.com) - Click Add Domain
Postscale will generate the DNS records you need to add.
DNS Records Overview
| Record Type | Purpose |
|---|---|
| SPF | Authorizes Postscale to send emails on your behalf |
| DKIM | Adds cryptographic signatures to verify email authenticity |
| DMARC | Tells receiving servers how to handle authentication failures |
| MX | Routes incoming emails to Postscale (for inbound processing) |
| CNAME | Enables custom tracking domains |
Sending Configuration
SPF Record
Add this TXT record to authorize Postscale:
Type: TXT
Host: @
Value: v=spf1 include:_spf.postscale.io ~all
If you already have an SPF record, add include:_spf.postscale.io before the ~all or -all:
v=spf1 include:_spf.google.com include:_spf.postscale.io ~all
DKIM Record
Add the DKIM record provided in your dashboard:
Type: TXT
Host: postscale._domainkey
Value: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4...
The DKIM key is unique to your domain and generated when you add the domain.
DMARC Record
Add a DMARC policy to specify how to handle authentication failures. When you add a domain, Postscale automatically generates a unique DMARC report address. The recommended record is shown in your domain's DNS settings:
Type: TXT
Host: _dmarc
Value: v=DMARC1; p=quarantine; rua=mailto:{your-address}@dmarc.postscale.io
Using the Postscale rua= address enables automatic DMARC aggregate report collection and analysis in your dashboard. See the DMARC Reports guide for details.
DMARC policies:
p=none— Monitor only, don't take actionp=quarantine— Send failures to spamp=reject— Reject failures outright
Start with p=none to monitor authentication results, then gradually move to quarantine and reject.
Receiving Configuration (Inbound)
To receive and process incoming emails, configure MX records:
MX Records
Add these MX records to route incoming emails to Postscale:
Type: MX
Host: @
Priority: 10
Value: mx1.postscale.io
Type: MX
Host: @
Priority: 20
Value: mx2.postscale.io
Subdomain for Inbound
For inbound-only processing, you can use a subdomain:
Type: MX
Host: inbound
Priority: 10
Value: mx1.postscale.io
This routes anything@inbound.yourcompany.com to Postscale while keeping your main domain's email unchanged.
Custom Tracking Domain
For link and open tracking, set up a custom tracking domain:
Type: CNAME
Host: track
Value: track.postscale.io
This enables tracking URLs like track.yourcompany.com/click/... instead of Postscale's default domain.
Verification
After adding DNS records, verify your domain:
- Return to the Domains section in the dashboard
- Click Verify Domain next to your domain
- Postscale will check your DNS records
DNS changes can take up to 48 hours to propagate, though most propagate within a few minutes.
Verification Status
| Status | Meaning |
|---|---|
| Pending | Waiting for DNS record verification |
| Verified | All records configured correctly |
| Partial | Some records verified, others pending |
| Failed | Records not found or incorrect |
Troubleshooting
SPF Record Not Found
- Ensure the TXT record is on the root domain (
@) - Check for typos in
include:_spf.postscale.io - Wait for DNS propagation and try again
DKIM Verification Failed
- Verify the host is exactly
postscale._domainkey - Check that the full value is copied without truncation
- Some DNS providers require the value without quotes
MX Records Not Working
- Ensure priority values are set (10 and 20)
- Check that no other MX records conflict
- Verify the records are on the correct host (@ for root, subdomain for subdomain)
Multiple Domains
You can add multiple domains to your Postscale account. Each domain requires its own DNS configuration but shares your API key and settings.
Common multi-domain setups:
- Main domain + subdomain for different email types
- Multiple brands under one account
- Separate domains for transactional vs marketing (if using marketing features)