Skip to main content

​
Overview

When you set up a custom email domain in Tightknit, you need to add DNS records so that email providers (Gmail, Outlook, etc.) can verify that messages sent from your domain are legitimate. Without these records, your emails may land in spam or be rejected entirely. This guide explains what each record type does and walks you through adding them at popular DNS providers.

​
Understanding the DNS records

SPF (TXT record)

Sender Policy Framework tells receiving mail servers which IP addresses are allowed to send email on behalf of your domain. It prevents others from spoofing your address.

DKIM (CNAME record)

DomainKeys Identified Mail adds a cryptographic signature to every outgoing message so receivers can verify the email was not altered in transit.

MX record

Mail Exchange records specify which servers handle incoming email for the domain. They are required for proper email routing and bounce handling.

​
General setup steps

1

Copy the DNS records from Tightknit

In the Email Domain settings, each required record is displayed with its Type, Host / Name, Value, and TTL. Use the copy button next to each value.
2

Log in to your DNS provider

Open the dashboard for the service where your domain’s nameservers are managed (e.g., Cloudflare, GoDaddy, or Namecheap).
3

Navigate to DNS management

Find the DNS records section for the domain or subdomain you are configuring.
4

Add each record

Create a new record for each entry shown in Tightknit. Make sure the Type, Name, and Value match exactly. See the provider-specific instructions below.
5

Verify in Tightknit

Return to the Email Domain settings page and click “I’ve added the records” to trigger verification.

​
Provider-specific instructions

  1. Log in to the Cloudflare dashboard and select the domain you are configuring.
  2. Go to DNS > Records.
  3. Click Add record.
  4. Select the correct Type (TXT, CNAME, or MX) from the dropdown.
  5. In the Name field, enter the value from the “Host / Name” column.
  6. In the Content (or Target) field, paste the value from the “Value” column.
  7. For MX records, enter the Priority value if one is provided.
  8. Set the Proxy status to DNS only (grey cloud) — mail records must not be proxied.
  9. Click Save and repeat for each record.
CNAME records used for DKIM must have the proxy toggled off (DNS only). Cloudflare proxying rewrites responses and will break DKIM verification.

​
Send a test email

After your domain is verified, you can confirm end-to-end deliverability by sending a test email directly from the settings page.
1

Navigate to Email Domain settings

Go to Settings > Notifications > Email Domain in the Admin Studio.
2

Click Send test email

Below the verified domain card, click the “Send test email” button. A test message will be sent from your custom domain to the email address associated with your admin account.
3

Check your inbox

Verify that the test email arrives in your inbox (check spam/junk if needed). The email is clearly labeled as a test and shows the sender address from your custom domain.
There is a short cooldown after sending a test email. Wait 30 seconds before sending another.

​
DNS propagation

After adding or updating DNS records, it can take time for the changes to propagate across the internet. Propagation times depend on your provider and the TTL (Time To Live) values.
  • Typical wait: 5 minutes to 1 hour for most providers.
  • Maximum: Up to 48 hours in rare cases.
  • TTL tip: If your provider lets you set a TTL, use a low value like 300 (5 minutes) while you are setting up. You can increase it later.

​
Troubleshooting

Double-check that each record’s type, name, and value match exactly what is shown in the settings page. Even an extra space or trailing period can cause verification to fail.
Make sure you select the correct type (TXT, CNAME, or MX) as shown in the “Type” column. Some DNS providers default to type A, which will not work.
Some DNS dashboards add surrounding quotes automatically. If yours does not, paste the value exactly as provided — do not add quotes yourself.
If there is already an SPF record for the domain, you may need to merge the new value into the existing record rather than creating a duplicate. Multiple SPF records for the same domain can cause delivery failures.
You can verify that records are published by using free online DNS lookup tools. Search for “DNS TXT lookup” or “DNS CNAME lookup” and enter your domain to see what is currently published.