Skip to content

article

Connect and verify a custom domain

How domain connection works across StretchSuite — proving ownership with a TXT record, then adding the routing records that point your domain at a Stretch app like StretchWP, StretchSites, or StretchMail.

The two-step model

Connecting a custom domain to any StretchSuite app follows the same two-step pattern:

  1. Prove ownership — publish a TXT record Stretch gives you. This proves you actually control the domain before Stretch will serve traffic for it.
  2. Point the domain — publish the routing records (usually a CNAME or A record) that direct visitors to the Stretch app.

Both steps happen at your DNS provider — the registrar or DNS host where your domain's nameservers live (for example your registrar, Cloudflare, etc.). Stretch generates the exact records; you publish them.

How to connect a domain

  1. Open the relevant app (Domains, or the app you're connecting the domain to — StretchWP, StretchMail, StretchSites) and start Add / connect a domain.
  2. Enter your domain (for example paynecoaching.ca).
  3. Stretch shows a verification TXT record — a host like _stretchsuite (or similar) and a unique value.
  4. In your DNS provider, create that TXT record exactly as shown.
  5. Return to Stretch and click Verify DNS. The status moves from Waiting for TXT to Ownership verified once it resolves.
  6. Stretch then shows the routing records (typically a CNAME pointing your domain at the app). Publish those too.
  7. Click Verify DNS again. When ownership and routing records both resolve, the domain becomes Verified / Active and starts serving.

Understanding the statuses

Domain connection moves through clear states:

  • Waiting for TXT — the ownership record hasn't resolved yet; publish it and wait for propagation.
  • Pending DNS — ownership is verified; finish the app-specific routing records.
  • Verified / Active — ownership and required routing records are all in place; the domain is live.

A realistic example

A coaching business built its site on StretchWP (currently on a temporary StretchMedia URL) and wants it live at paynecoaching.ca:

  1. In StretchWP, they start the domain connection for paynecoaching.ca.
  2. Stretch shows a TXT record; they add it at their registrar and click Verify DNS — status becomes Ownership verified.
  3. Stretch shows a CNAME to point the domain at the site; they add it.
  4. They click Verify DNS once more; after propagation the domain shows Active and the site loads at paynecoaching.ca with HTTPS.

Troubleshooting

"Waiting for TXT" won't clear — check for a typo, and watch for your DNS provider auto-appending the domain to the host name (creating a doubled name). The record type must be TXT, and the value must match exactly.

Ownership verified but the site won't load — you still need the routing record (CNAME/A). Ownership alone doesn't route traffic.

CNAME conflicts with the root domain — many DNS providers won't allow a CNAME on the bare root (example.com). Use the provider's flattening/ALIAS/ANAME option, or connect via www and redirect the root, or follow the exact record Stretch specifies.

It verified earlier but broke later — someone may have edited or removed the DNS records, or nameservers changed. Re-check that all Stretch-provided records still exist.

HTTPS/certificate warning right after connecting — certificates provision shortly after the domain verifies; give it a little time and reload.

Tips

  • Lower your TTL a day before connecting if you want faster propagation.
  • Don't delete the ownership TXT record after verifying — leave Stretch's records in place; removing them can break the connection later.
  • Keep your registrar/DNS login handy — you'll need it for the whole flow, and again if you ever move the domain.
  • One domain, one purpose at a time for routing — pointing the same host at two services causes conflicts.

FAQ

Do I have to transfer my domain to Stretch? No. You keep your domain at your current registrar; you only add DNS records that point it at Stretch.

How long does it take? Usually minutes to a couple of hours, gated entirely by DNS propagation.

Can I connect the same domain to more than one app? You can use subdomains for different apps (for example the root for your site and mail. for email), but each host should point at one service. Follow the exact records each app provides.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.