Custom Domain Setup

Birdie allows you to serve recordings and related assets from your own domain. This configuration requires adding two DNS CNAME records and completing automatic TLS validation.

Prerequisites

• A domain you control (e.g. yourdomain.com).

• Access to your DNS provider.

---

Step 1 – Register Your Domain in Birdie

1. Open your Birdie Workspace

2. Go to Settings → Incoming Recordings → Identity

3. Click Add custom domain

4. Enter your Apex Domain (without subdomain), e.g.: yourdomain.com

Birdie will automatically provision and use a subdomain such as: capture.yourdomain.com . This subdomain will serve recordings and related assets.

---

Step 2 – Configure Domain Ownership & Traffic Routing

Add the first CNAME record exactly as provided in the Birdie interface.

Example (values will differ):

capture.yourdomain.com → cname1.birdie.so.

⚠️ Important: Do not modify the target value. Do not replace CNAME with A/AAAA, or ALIAS records records.

DNS propagation typically completes within a few minutes but may vary depending on your DNS provider.

Once this record is detected, Birdie will automatically proceed with TLS certificate validation.

---

Step 3 – Configure TLS Certificate Validation

Add the second CNAME record exactly as provided.

Example (values will differ):

_f9dcaeb739484679a5764a5ac717a75b.capture.yourdomain.com → _e9fd41ca3c25865c9a3dbdedbe5275e1.jkddrztszm.acm-validations.aws.

⚠️ Important: Do not modify the target value. Do not replace CNAME with A/AAAA, or ALIAS records records.

After DNS propagation, AWS Certificate Manager (ACM) will automatically validate the certificate. No additional action is required.

---

Step 4 – Automatic Activation

When both CNAMEs resolve correctly:

• Domain ownership is verified

• TLS certificate is issued automatically

• The domain becomes active

• Status updates are reflected in the Birdie UI

No manual approval or support intervention is required.

---

Custom Storage Buckets & CORS (Important)

If you do not use a custom bucket, you may skip this section.

If you use a custom storage bucket (AWS S3, Google Cloud Storage, or Azure Blob Storage), you must update your CORS configuration.

Add your new fully qualified domain name (FQDN) to the allowed origins list:

https://capture.yourdomain.com

Example for AWS S3 CORS Policy:

[
    {
        "AllowedHeaders": ["*"],
        "AllowedMethods": ["GET","PUT","POST","HEAD"],
        "AllowedOrigins": [
            "https://*.birdie.so",
            "https://capture.yourdomain.com"
        ],
        "ExposeHeaders": [],
        "MaxAgeSeconds": 3000
    }
]

This configuration is required for:

• Video playback

• Recording uploads

• Web recorder access

If not configured correctly, browsers will block requests due to CORS policy restrictions.

---

Update Your Integrations

After activating your custom domain, update any existing integrations or hardcoded URLs.

For example:

yourdomain.birdie.so → capture.yourdomain.com

Common locations requiring updates:

• Helpdesk signatures

• Helpdesk macros

• Email templates

• Automated workflows

---

Troubleshooting

• Ensure both DNS records are configured as CNAME (not A, AAAA, or ALIAS)

• Verify DNS propagation: dig capture.yourdomain.com

• Confirm there are no conflicting DNS records

• For CORS-related issues, review browser console errors first

---

Once validation completes, Birdie will securely serve all recording traffic from your custom domain.