Sender Domain Setup
Verifying your own sender domain tells email providers that Synapse is authorized to send on behalf of your domain, which improves deliverability and puts your brand on every email. It is an optional upgrade — you can go live and send on Synapse's shared pyrx.tech domain with no setup at all. This page is the full reference for DNS setup, verification, and troubleshooting for when you're ready to add your own domain.
For the quick-start walkthrough, see Set Up Sender Domain.
Why Add a Custom Domain
You can send on Synapse's shared domain ([email protected]) on any plan, in both test and live mode, with nothing to configure. Verifying your own domain is an optional upgrade that adds three things for production sending:
- Higher trust. Recipients and email providers trust emails from your own domain more than a shared one.
- Your brand in the "From" address. Customers see
yourcompany.cominstead ofpyrx.tech. - Isolated reputation. Your sender reputation is your own, rather than pooled with other workspaces on the shared domain.
A custom domain gives you full control over your sender reputation and brand presentation. It is recommended for production, but it is not required to go live — you can add it any time, and until it verifies your sends continue to go out on the shared domain.
Adding a Domain
- Go to Settings > Sender Domains in the dashboard.
- Click Add Domain.
- Enter the domain name (e.g.,
yourcompany.comormail.yourcompany.com). - Click Continue.
Synapse generates the DNS records you need to add to your domain's DNS configuration and automatically detects which DNS provider hosts your domain. The domain starts in Pending status until verification passes.
Only Owners and Admins can add and manage sender domains. Developers have read-only access. Marketing, Operations, and Viewer roles have no access.
DNS Provider Auto-Detection
When you add a domain, Synapse automatically detects your DNS provider and displays it with a branded icon on the domain detail page. The detected provider name links directly to your provider's DNS management panel, so you can jump straight to where you need to add records.
Supported Providers
Synapse recognizes the following DNS providers:
| Provider | DNS Management Link |
|---|---|
| Cloudflare | dash.cloudflare.com |
| Namecheap | ap.www.namecheap.com (direct link to your domain) |
| GoDaddy | dcc.godaddy.com (direct link to your domain) |
| AWS Route 53 | console.aws.amazon.com/route53 |
| Google Cloud DNS | console.cloud.google.com |
| DigitalOcean | cloud.digitalocean.com |
| NS1 | my.nsone.net |
| Hetzner | dns.hetzner.com |
| Vultr | my.vultr.com/dns |
| Linode (Akamai) | cloud.linode.com/domains |
| Hover | hover.com/control_panel |
| DNSimple | dnsimple.com/dashboard |
| Dyn (Oracle) | cloud.oracle.com |
| Vercel | vercel.com/dashboard/domains |
| WordPress.com | wordpress.com/domains |
If your provider isn't in this list, Synapse shows it as "DNS Provider" and you can still set up your domain manually.
DNS Records Explained
After adding your domain, Synapse provides four DNS records. Each serves a different purpose in email authentication:
1. SPF (Sender Policy Framework)
| Detail | Value |
|---|---|
| Type | TXT |
| Host | @ (your root domain) |
| Value | v=spf1 include:send.resend.dev ~all |
| Purpose | Tells receiving mail servers that Synapse's email infrastructure is authorized to send emails for your domain |
If you already have an SPF record for your domain (e.g., for Google Workspace or Microsoft 365), merge them into a single record. SPF allows only one TXT record per domain. For example: v=spf1 include:_spf.google.com include:send.resend.dev ~all
2. DKIM (DomainKeys Identified Mail)
| Detail | Value |
|---|---|
| Type | CNAME |
| Host | resend._domainkey |
| Value | resend.domainkey.resend.dev |
| Purpose | Adds a cryptographic signature to every email, letting recipients verify the message hasn't been tampered with |
3. DMARC (Domain-based Message Authentication)
| Detail | Value |
|---|---|
| Type | TXT |
| Host | _dmarc |
| Value | v=DMARC1; p=none; |
| Purpose | Tells receiving servers what to do when SPF or DKIM checks fail. Starting with p=none means "report but don't block" -- a safe starting point |
Once you're confident in your email authentication setup, consider tightening your DMARC policy to p=quarantine or p=reject. This is an advanced step -- see your DNS provider's documentation for guidance.
4. Ownership Verification
| Detail | Value |
|---|---|
| Type | TXT |
| Host | @ (your root domain) |
| Value | synapse-verify={unique_hash} |
| Purpose | Proves that you control this domain. The hash is unique to your workspace. |
Adding Records to Your DNS Provider
Synapse detects your DNS provider automatically and shows a direct link to your provider's DNS management panel on the domain detail page. Click the provider name to open your DNS settings in a new tab.
If your provider is not auto-detected, use the general steps below.
General Steps
- Log into your DNS provider.
- Navigate to the DNS management page for your domain.
- Add each record with the type, host, and value shown in the Synapse dashboard.
- Save your changes.
Some DNS providers automatically append your domain to the host value. If Synapse shows the host as resend._domainkey, your provider might require just resend._domainkey (without the domain) or resend._domainkey.yourcompany.com (with it). Check your provider's documentation if you're unsure.
Auto-Configure with Cloudflare (Domain Connect)
If your domain uses Cloudflare nameservers, Synapse detects this automatically and offers one-click DNS setup via the Domain Connect protocol. This adds all required DNS records (SPF, DKIM, DMARC, and ownership verification) to your Cloudflare zone without any manual entry.
How It Works
- Add your domain in Synapse. Synapse detects that it uses Cloudflare.
- On the domain detail page, click the Auto configure button (shown with the Cloudflare icon).
- You are redirected to Cloudflare's authorization page.
- Click Authorize on Cloudflare to allow Synapse to add the DNS records.
- You are redirected back to Synapse. The records are configured automatically.
- Synapse auto-verifies the DNS records. Your domain shows as Verified with all records confirmed.
The entire auto-configure flow typically completes in under 30 seconds. No manual DNS entry, no waiting for propagation.
What Gets Configured
When you authorize Domain Connect, Cloudflare automatically adds all four DNS records:
- SPF TXT record
- DKIM CNAME record
- DMARC TXT record
- Ownership verification TXT record
If Auto-Configure Fails
If the authorization is cancelled or encounters an error, Synapse shows the failure on the domain detail page. You can:
- Retry by clicking the auto-configure button again.
- Fall back to manual setup by adding the DNS records yourself using the values shown in the dashboard.
Auto-configure via Domain Connect is currently available for Cloudflare-hosted domains. Support for additional providers is coming. For all other providers, add the DNS records manually.
Verifying Your Domain
After adding the DNS records (either manually or via auto-configure):
- Go to Settings > Sender Domains.
- Click on your domain to open the detail page.
- Click Verify.
Synapse checks each DNS record individually using DNS-over-HTTPS (via Cloudflare's public resolver). The detail page shows a per-record status:
| Record Status | Meaning |
|---|---|
| Verified | The record was found and matches the expected value |
| Not found | The record hasn't propagated yet, or hasn't been added |
Domain Status
| Status | Meaning |
|---|---|
| Pending | One or more DNS records haven't been verified yet |
| Verified | All four records are confirmed -- you can send from this domain |
| Failed | Records are incorrect or missing after multiple checks |
DNS propagation can take anywhere from a few minutes to 48 hours, depending on your provider and TTL settings. If verification fails right after adding records, wait 30 minutes and try again. If you used auto-configure with Cloudflare, verification is nearly instant.
Troubleshooting DNS Issues
Verification keeps failing
- Check for typos. Copy values directly from the Synapse dashboard. Even an extra space or missing character will cause failure.
- Check for duplicates. Some providers already have an SPF or DMARC record. Having two SPF TXT records on the same host is invalid -- merge them.
- Check host format. Some providers want
resend._domainkey, others wantresend._domainkey.yourcompany.com. If one doesn't work, try the other. - Check record type. Make sure the DKIM record is a CNAME, not a TXT. The SPF and DMARC records must be TXT, not CNAME.
- Wait for propagation. Allow at least 1 hour before retrying. Some providers (especially less common registrars) can take up to 48 hours.
Records show as verified but domain is still "Pending"
All four records must pass verification. Click into the domain detail page to see which specific record is still failing.
Auto-configure button not showing
- The auto-configure button only appears for domains hosted on Cloudflare. If your domain uses a different DNS provider, you need to add records manually.
- If your domain is on Cloudflare but the button doesn't appear, try refreshing the page. Synapse re-detects the DNS provider on each page load if it hasn't been cached yet.
Emails still going to spam after verification
- Allow 2-3 days for email providers to build trust with your new sending domain.
- Make sure your DKIM record is verified (not just SPF).
- Check that your email content isn't triggering spam filters (misleading subject lines, excessive links, etc.).
- Consider tightening your DMARC policy from
p=nonetop=quarantineonce you're confident all legitimate emails pass SPF and DKIM.
I changed my DNS records and need to re-verify
- Go to Settings > Sender Domains.
- Click on the domain.
- Click Verify to trigger a fresh DNS check.
Synapse will re-check all records and update each record's status individually.
Deleting a Domain
If you no longer need a sender domain:
- Go to Settings > Sender Domains.
- Click on the domain.
- Click Delete.
Deleting a domain means you can no longer send emails from addresses on that domain. Any flows using templates with a "From" address on the deleted domain will fail to send. Update your templates before deleting.
Next Steps
- Set Up Sender Domain -- the quick-start walkthrough
- Write Your First Template -- start creating emails
- Workspace Settings -- configure your default sender identity