Custom domains

Add a custom domain to serve your application at an address such as app.example.com or example.com. Custom domains are available for web services and static sites.

You need access to the domain's DNS provider and a deployed service. Domain registration is separate from hosting on Openstead.

Add a hostnameCopy Anchor Link

1. Open your service's Settings → Custom Domains section.
2. Select Add Custom Domain.
3. Enter the hostname without https://, a port, or a path.
4. Add the DNS records shown by Openstead at your DNS provider.

Add every hostname separately. example.com and www.example.com are different hostnames. Openstead supports up to 20 custom hostnames per service; wildcard hostnames are not supported by this flow.

Publish the ownership recordCopy Anchor Link

Openstead displays a TXT record with a name such as _runivo-challenge.app.example.com and a generated value. Copy its exact value from the dashboard.

The TXT record proves that you control the hostname. Keep it in DNS. If your provider automatically appends example.com to record names, enter only the appropriate relative label, such as _runivo-challenge.app.

Point traffic to OpensteadCopy Anchor Link

For a subdomain, add the supplied CNAME record:

For a root domain, use the displayed Root domain alternative A record:

Use your actual dashboard values, not another service's hostname or IP. Remove conflicting A or AAAA records for the same hostname. There must not be an IPv6 route pointing somewhere else.

If your DNS provider proxies traffic, use DNS-only mode. See Cloudflare DNS for its exact record setup.

Wait for automatic verificationCopy Anchor Link

Openstead begins checking when you add the domain and retries automatically. The modal and domain list update as DNS and HTTPS checks finish. You can close the modal; the background verification continues.

Verify DNS requests another check, but repeatedly pressing it cannot make your DNS provider propagate records faster.

Domain verification and certificate issuance are separate steps:

1. Openstead finds the expected ownership TXT record.
2. The hostname resolves to the service's expected IPv4 destination without conflicting records.
3. Openstead configures the route and obtains an HTTPS certificate.
4. The domain is ready when verification and HTTPS are both complete.

Configure your applicationCopy Anchor Link

After connecting the domain, update application settings that depend on its public URL. Examples include Laravel's APP_URL, Django's allowed hosts and CSRF origins, OAuth callback URLs, CORS allowlists, and transactional-email links.

DNS does not automatically configure redirects between an apex domain and www. Add the needed hostnames and configure any canonical-host redirect in the application or an appropriate routing rule.

Keep or disable the Openstead addressCopy Anchor Link

The generated Openstead address can remain enabled beside the custom domain. You can disable it after at least one custom domain has verified HTTPS.

If you later remove the last verified custom domain, first re-enable the Openstead subdomain so the service retains a usable public address.

Troubleshoot a pending domainCopy Anchor Link

• Check the exact TXT name and value, including whether the DNS provider duplicated the zone name.
• Confirm the service is deployed and its target is current.
• Remove stale A or AAAA records and disable proxying.
• Check both www and the root separately if both should work.
• If DNS is verified but HTTPS is pending, follow HTTPS troubleshooting.

Deleting a domain in Openstead removes its route. It does not edit or delete records at your DNS provider.