Custom domains
Point your own domain at the app, with HTTPS.
A domain you own is what makes an app feel real.
Before you start
- Own the domain and be able to change its DNS records wherever you bought it.
- Decide whether you want the bare domain (
yourstudio.com) or a subdomain (app.yourstudio.com). - Know who can approve DNS changes. It is often not the person building.
Adding the domain
Add the domain from your project's domain settings, or ask in the chat how to connect it. You will be shown which DNS records to create. Copy them into your DNS provider exactly as shown.
Then wait. DNS changes are usually quick but can take up to a few hours to propagate.
HTTPS
Once the domain is verified, a certificate for HTTPS is set up for you.
Redirects and both versions
Decide which address is canonical, yourstudio.com or www.yourstudio.com, and redirect the other to it. Otherwise you end up with split links.
Email on the same domain
Adding the app's DNS records should not touch your email. Be careful with MX and root-level records: only change the records you were given, and leave the rest alone.
Common problems
- Verification stays pending: the record is on the wrong host or has the wrong name. Check for an extra prefix added by your DNS provider.
- Shows a default page: the routing record is missing, or points somewhere else.
- Certificate warning: wait a little longer, then check the verification record is still in place.
Set up the domain before you announce anything. It is much easier to test quietly than to chase a fix after a launch.
Next: Preview and live versions.
Was this page helpful?