Channels

DNS Configuration

Overview

To send and receive emails through There There, you need to configure DNS records for your domain. This involves three steps: verifying domain ownership, setting up DKIM for email authentication, and configuring the return path for bounce handling.

Domain ownership verification

When you create an email channel, There There generates a unique verification token. Add the following TXT record to your domain's DNS:

Type:  TXT
Host:  @  (or your root domain)
Value: there-there-verification=<your-verification-uuid>

There There will check for this record automatically. Once found, your domain ownership is confirmed.

DKIM setup

DKIM (DomainKeys Identified Mail) lets receiving mail servers verify that emails were genuinely sent from your domain. After domain verification, There There provides the DKIM record values. Add a TXT record:

Type:  TXT
Host:  <provided-dkim-hostname>
Value: <provided-dkim-value>

The exact hostname and value are displayed in your channel's DNS settings page. They are unique to your domain.

Return path configuration

The return path record ensures that bounced emails are handled correctly. Add a CNAME record:

Type:  CNAME
Host:  pm-bounces  (or the hostname shown in your settings)
Value: <provided-return-path-cname>

Verification

There There periodically checks your DNS records and updates the verification status in your channel settings. You can also trigger a manual check from the channel's DNS settings page. All three records (ownership TXT, DKIM TXT, and return path CNAME) must be verified before your channel can send emails.

Common DNS providers

The steps above apply to all DNS providers, but the interface differs. Here are some notes for popular providers:

  • Cloudflare: Add records in the DNS management section. For CNAME records, disable the proxy (orange cloud) so the record resolves correctly.
  • Namecheap: Use the "Advanced DNS" tab. For the host field, omit your domain name (e.g. use pm-bounces instead of pm-bounces.yourcompany.com).
  • Google Domains / Squarespace: Add records under "DNS" in the domain settings. Use @ for the root domain host.

Troubleshooting

If verification is not completing, check the following:

  • Propagation time: DNS changes can take up to 48 hours to propagate, though most providers update within minutes.
  • Correct host format: Some providers require the full hostname (e.g. pm-bounces.yourcompany.com) while others only need the subdomain part (pm-bounces).
  • No conflicting records: Make sure there are no duplicate or conflicting TXT/CNAME records for the same hostname.
  • Proxy disabled: If using Cloudflare, ensure the CNAME record is set to "DNS only" (gray cloud).