Connecting a custom domain to a cloud-hosted app is more than adding a DNS record. This reusable checklist covers domain verification, SSL certificates, apex and subdomain routing, redirects, preview environments, and multi-tenant policies so your next domain launch is predictable and easier to troubleshoot.
Overview
A custom domain cloud app setup has four moving parts: the domain registrar, DNS provider, hosting or app platform, and the application’s routing layer. A failure in any one of them can produce similar symptoms, such as a certificate warning, a 404 page, an infinite redirect, or a domain that reaches the wrong tenant.
Before making changes, document the intended hostname and traffic path. For example, decide whether customers will use app.example.com, an apex domain such as example.com, or individual domains such as customer.example.org. Then identify where DNS is managed, where the app is deployed, and which service is responsible for issuing certificates.
Do not treat a platform’s default preview URL as equivalent to production. Preview domains are useful for testing builds, but production traffic should have a documented domain, certificate, redirect policy, and rollback path. For deployment context, compare this work with the release controls in the cloud app staging environment checklist and the guidance on preview environments for web apps.
Provider comparison worksheet
Features and limits change by provider, product, plan, and account configuration. Use the table below during evaluation, then confirm each item in the provider’s current documentation before committing to an architecture.
| Provider or platform type | Custom-domain questions to verify | Best fit to investigate |
|---|---|---|
| Vercel | Domain limits, apex and subdomain support, wildcard behavior, certificate automation, API operations, and preview-domain controls | Frontends and server-rendered web apps with preview-heavy workflows |
| Netlify | Domain limits, DNS verification options, redirects, wildcard support, certificate lifecycle, and API access | Static sites, frontend applications, and teams using configuration-based redirects |
| Cloudflare Pages or Workers | Custom-hostname model, wildcard and apex behavior, certificate ownership, DNS delegation requirements, and tenant-routing options | Applications already using Cloudflare’s edge, DNS, or serverless services |
| Render or similar managed app hosting | Service-to-domain mapping, certificate provisioning, redirect configuration, domain verification, and automation interfaces | Web services where the application and deployment service are managed together |
| Container platform with an ingress controller | Ingress rules, certificate issuer, DNS automation, wildcard certificates, renewal monitoring, and operational ownership | Teams that need routing control across several services or clusters |
For a broader platform decision, record these answers alongside support, limits, portability, and exit-risk questions in the cloud app platform evaluation scorecard.
Checklist by scenario
For one production domain
- Confirm the exact hostname: apex,
www, or another subdomain. - Find the platform’s required verification record and target record. Do not substitute values from another project or environment.
- Lower the DNS record’s TTL before a planned migration if your DNS provider permits it. Restore an appropriate TTL after validation.
- Add the record, complete platform verification, and wait for DNS visibility.
- Confirm that the certificate covers the exact hostname and that HTTPS is active.
- Choose one canonical hostname and redirect the other hostname to it.
- Test the homepage, authenticated routes, API calls, assets, forms, and error pages over HTTPS.
For a SaaS customer domain
- Define whether the customer points a subdomain, such as
app.customer.com, or an apex domain, such ascustomer.com. - Give the customer a short DNS worksheet containing record type, host, destination, verification value, and expected status.
- Store the verified hostname separately from the tenant identifier. A hostname must not become an implicit authorization decision.
- Require domain verification before serving tenant content. Keep the verification state, timestamp, and responsible account in an auditable record.
- Route the request using the validated host, then apply tenant authorization in the application.
- Define what happens when a domain is removed, a customer changes providers, or verification expires.
Multi-tenant routing should be reviewed with the same care as authentication and permissions. The low-code app security checklist is useful even when your app is built with conventional code, because hostname routing can expose data if tenant boundaries are incomplete.
For a rebrand or DNS migration
- Inventory every hostname, including API endpoints, webhooks, admin tools, documentation, and old campaign URLs.
- Issue and validate the new certificate before switching traffic.
- Deploy redirects at the correct layer and preserve paths and query parameters where appropriate.
- Update allowlists, OAuth callback URLs, CORS settings, cookies, webhooks, email links, and monitoring checks.
- Keep the old domain active long enough to observe traffic and resolve forgotten integrations.
DNS record worksheet
Complete this worksheet before asking a customer or administrator to change DNS:
| Field | Value to record |
|---|---|
| Hostname | Exact name, including whether it is apex or subdomain |
| Record type | A, AAAA, CNAME, TXT, or the type specified by the platform |
| Host/name | Provider-specific host notation |
| Destination/value | Current platform target or verification token |
| Purpose | Routing, ownership verification, certificate validation, or redirect support |
| Expected result | Verified status, HTTPS response, or canonical redirect |
What to double-check
- Apex behavior: An apex domain may not accept a CNAME in the same way a subdomain does. Follow the DNS provider’s supported alias, flattening, or platform-specific method rather than guessing.
- Certificate scope: A certificate for
example.comdoes not automatically imply coverage for every possible subdomain. Confirm the names and wildcard scope explicitly. - DNS verification: Remove stale verification records only after the platform confirms ownership and you understand whether renewal or future changes depend on them.
- Redirect order: Decide whether redirects happen at the edge, hosting layer, proxy, or application. Multiple layers can create loops or hide the original request.
- Cookies and sessions: Changing from a platform hostname to a custom hostname can affect cookie domains, secure flags, OAuth callbacks, and CSRF origins.
- API and webhook dependencies: Update third-party integrations deliberately. For webhook changes, preserve signature validation, retries, and idempotency as described in the reliable webhook integrations guide.
- Observability: Monitor certificate expiry, DNS resolution, HTTP status codes, redirect chains, and tenant-to-host mappings rather than checking only whether the homepage loads.
Common mistakes
- Changing nameservers when only a record was required: This can move control of unrelated services such as email. Confirm whether the instruction concerns a record or delegation.
- Testing from one network only: Resolver caches and propagation can differ. Check authoritative DNS and use more than one resolver before declaring the migration complete.
- Assuming certificate issuance is immediate: Verification, DNS visibility, platform queues, and rate controls can all affect timing. Keep the old route available during a planned cutover.
- Using wildcard routing without tenant safeguards: A wildcard certificate or DNS record does not prove that a request belongs to the correct customer.
- Forgetting non-browser clients: Mobile apps, command-line tools, background jobs, and partner integrations may still call the old hostname.
- Leaving preview domains unrestricted: Preview URLs can expose unfinished features or data. Apply access controls and safe data rules before sharing them externally.
When to revisit
Review this checklist before every new customer domain, rebrand, certificate or DNS migration, and recurring domain audit. Recheck it before seasonal planning cycles and whenever your hosting provider changes domain limits, certificate behavior, DNS instructions, API capabilities, preview-domain rules, or pricing.
Make the process operational rather than personal: keep the DNS worksheet in the project record, assign ownership for certificate and DNS monitoring, and test a representative custom domain after deployment changes. During each review, remove abandoned records, confirm redirects, validate tenant mappings, and check that documentation matches the platform’s current interface.
For the next domain, use this order: document the hostname, verify the platform requirements, add DNS, confirm certificate coverage, test routing and redirects, update integrations, and record the final state. That sequence turns a fragile one-off change into a repeatable app deployment practice.