Skip to main content

Configure a Custom Email Domain in Pyn

Set up e-mail senders from your company addresses

Written by Julianna Kapjian-Pitt
Updated over 2 weeks ago

Connecting a custom email domain allows you to send employee communications from your own branded address (e.g. people@yourcompany.com) instead of a generic sender. This helps build trust, improve deliverability, and create a more cohesive employee experience.

This guide walks you through adding, verifying, and managing a custom sender domain in Pyn.


Why set up a custom domain?

With a verified custom domain, you can:

  • Send messages from your company’s email address

  • Improve email deliverability and trust

  • Maintain consistent branding across employee communications

  • Set a default sender for automated flows

Once verified, you’ll be able to use that domain across onboarding, milestone messaging, manager nudges, and more.


Step 1: Add a Custom Domain

  1. Go to SettingsIntegrations Available

  2. Click Email

  3. Click the "..." menu and then Add Custom Domain

  4. Enter your domain (e.g. mail.yourcompany.com)

  5. Click Add

When you add the domain, Pyn will generate DNS records through SendGrid for verification.


Step 2: Add DNS Records

After adding your domain, you’ll see several DNS records that need to be configured.

These records typically include:

  • CNAME entries

  • Host values

  • Target values

To complete this step:

  1. Copy each DNS record provided in Pyn

  2. Go to your domain provider (e.g. GoDaddy, Cloudflare, etc.)

  3. Open your DNS settings

  4. Paste the values exactly as shown

  5. Save each record

💡 You’ll usually need to add three DNS records. DNS records tell the internet which services are authorized to send email on behalf of your domain. Without this step, verification will fail.


Step 3: Request Verification

Once your DNS records are saved:

  1. Return to Pyn

  2. Open the domain you just added

  3. Click Request Verification

Pyn will check the DNS records via SendGrid.

What to expect:

  • If records are missing or incorrect, you’ll see validation errors.

  • If some records are correct, you may see partial success.

  • Once all records are properly configured, the domain status will update to Verified.

⏳ Note: DNS changes can take a few minutes to propagate. If verification fails, wait a few minutes and try again.


Unverified Domains

If verification fails:

  • You’ll see an Unverified status.

  • Pyn will display the required DNS values again for reference.

  • You can recheck your DNS provider and try verification again.

A domain must be fully verified before it can reliably send email.


Set a Default Sender

Once a domain is verified, you can:

  • Mark it as Default

  • Use it across automated flows and campaigns

Only verified domains should be set as default to ensure reliable delivery.


Delete vs. Archive: What’s the Difference?

When managing domains, you have two options:

Archive (Recommended)

  • Removes the domain from active use in Pyn

  • Keeps it in SendGrid

  • Acts as a “soft delete”

  • Preserves verification settings

Best for temporary deactivation.

Delete (Permanent)

Deleting a domain will:

  • Remove it from Pyn

  • Fully delete it from SendGrid

  • Remove all associated verification records

You’ll see a confirmation warning before deletion.

⚠️ Deleting is permanent. If you re-add the domain later, you’ll need to complete verification again.


Troubleshooting

Verification failing?

  • Double-check that all DNS records are added exactly as shown.

  • Confirm there are no typos or extra spaces.

  • Wait a few minutes and try again (DNS propagation can take time).

No default sender selected?

  • If you delete your default domain, you’ll need to assign a new verified domain as default.

Did this answer your question?