> ## Documentation Index
> Fetch the complete documentation index at: https://help.sendspark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Domain Migration

> Step-by-step guide to migrating your custom domain in Sendspark, ensuring uninterrupted video delivery and consistent brand experience.

To migrate a custom domain in Sendspark: contact support to remove your current domain, add the new subdomain in **Settings → Custom Domain** (this generates the IP address), create a fresh DNS A record pointing to that IP, set a 301 permanent redirect from the old domain to the new one so existing links keep working, then wait for DNS to propagate. Don't delete the old domain.

## Key takeaways

* Follow the order: contact support to remove the old domain → add the new subdomain (this generates the IP) → create a fresh A record → set a 301 redirect → wait for propagation.
* Keep the old domain live — the 301 permanent redirect from old to new links depends on it.
* CAA records can block automatic SSL issuance; ask IT to allow Google's provider (`pki.goog`) or remove restrictive CAA settings.
* DNS propagation can take up to 24 hours; don't launch new campaigns until the domain is fully propagated and verified in Sendspark.

## 🧩 What you need before starting

🌐 New subdomain ready (e.g. `watch.newdomain.com`)\
🔧 Access to DNS settings (Cloudflare, Route 53, GoDaddy, etc.)\
⏰ Schedule a low-traffic window (recommended: off-peak hours)\
📌 Ability to create A records and redirects

***

## 🪜 Migration steps

***

## 1️⃣ Contact Support

Request removal of your current custom domain.

We’ll confirm once it has been fully removed on our side.

***

## 2️⃣ Add New Domain in Sendspark

Go to **Settings → Custom Domain** and add your new subdomain.

⚠️ The IP address is generated only at this step (it cannot be known in advance).

***

## 3️⃣ Create DNS A Record

Add a new A record in your DNS provider.

➡️ Point `watch.newdomain.com` → Sendspark IP address

## ⚠️ Important DNS rules:

* Do not reuse existing DNS records
* Create a fresh record every time
* Add it immediately after receiving the IP
* Avoid duplicate or conflicting record names
* If your DNS provider requires it, set the record to **DNS only (not proxied)**
  * In Cloudflare, this is typically the default behavior unless manually proxied

***

## ⚠️ Possible DNS Security Restriction (CAA)

In some cases, your domain may have additional DNS security settings configured by your IT or security team.

These settings (called **CAA records**) control which providers are allowed to issue SSL certificates for your domain.

If these restrictions are in place, Sendspark may not be able to generate a secure certificate automatically — even if your A record is set up correctly.

## What to do

If your domain doesn’t verify, you may need to:

* Ask your IT team to allow Google’s certificate provider (`pki.goog`), or
* Remove any restrictive CAA settings

***

## 4️⃣ Set Up 301 Redirect (Critical)

This ensures old links keep working without interruption.

🔁 Configure a **301 Permanent Redirect**

Mapping:

`watch.olddomain.com/*` → `watch.newdomain.com/*`

⚠️ Do NOT delete the old domain — it is required for redirects to function properly.

***

## 5️⃣ Wait for Propagation

⏳ DNS propagation can take up to 24 hours.

Once everything resolves, Sendspark will automatically verify your new domain.

***

## 📊 What changes during migration

| Scenario                                 | Result                            |
| ---------------------------------------- | --------------------------------- |
| Old link clicked before redirect         | ❌ Temporary broken page           |
| Old link clicked after redirect          | ✅ Seamless redirect to new domain |
| New campaigns after migration            | ✅ Use new domain only             |
| Existing embed codes in emails/templates | 🔄 Must be updated manually       |

***

## ⚠️ Important

Do not launch new campaigns until:

✔ DNS is fully propagated\
✔ Domain is verified in Sendspark

This ensures clean URLs and avoids deliverability issues.

***

## 🆘 Need help?

Contact Sendspark support to start the process or if anything looks off during setup.

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why can't I set up the A record before adding the domain?">
    The IP address is generated only when you add the new subdomain in Settings → Custom Domain — it can't be known in advance. Add the domain first, then create a fresh A record pointing to the IP you receive.
  </Accordion>

  <Accordion title="Can I reuse my existing DNS record?">
    No. Create a fresh A record every time, add it immediately after receiving the IP, and avoid duplicate or conflicting record names. If your DNS provider requires it, set the record to DNS only (not proxied).
  </Accordion>

  <Accordion title="Should I delete the old domain after migrating?">
    No. Do not delete the old domain — the 301 permanent redirect (mapping `watch.olddomain.com/*` → `watch.newdomain.com/*`) needs it to keep existing links working.
  </Accordion>

  <Accordion title="My domain won't verify — what should I check?">
    Your domain may have CAA records set by your IT or security team that control which providers can issue SSL certificates. Ask IT to allow Google's certificate provider (`pki.goog`) or remove the restrictive CAA settings.
  </Accordion>

  <Accordion title="How long does the migration take to go live?">
    DNS propagation can take up to 24 hours. Once everything resolves, Sendspark automatically verifies the new domain. Don't launch new campaigns until DNS is fully propagated and the domain is verified.
  </Accordion>
</AccordionGroup>

## Related articles

* [Use a Custom Domain for Videos](/use-a-custom-domain-for-videos)
* [Remove Sendspark Branding (Whitelabel)](/remove-sendspark-branding-whitelabel)

*Updated July 2026.*