D3. Point your domain to your app
What this page helps you do
Point your domain to the real place your app is hosted.
Why it matters
Many “the app is down” reports are really domain or DNS problems. The app can be alive while the domain points to the wrong place.
You should already have
- a live hosting target
- control of your DNS settings
- Cloudflare set up, if you are using it
Skip this page if
- the domain already resolves to the right app and you verified it
Then go to D4. HTTPS and SSL or R8. Launch checklist.
What to do
- Find the correct target from your hosting provider or server setup.
- Create the DNS record in Cloudflare or your DNS provider.
- Wait for the record to update.
- Test the root domain and any
wwwsubdomain you want to use. - Confirm the app responds from the real domain, not only the platform URL.
Depending on the host, you may need:
- an
Arecord that points to an IP address - a
CNAMErecord that points to another hostname
In plain English, both record types tell the domain where the app lives.
Recommended default
Use the smallest number of DNS records needed to make the app work clearly.
Common mistakes
- pointing the domain at an old server
- forgetting the
wwwversion - testing too early and assuming nothing worked
- not adding the custom domain inside the hosting provider as well
Next step
Go to D4. HTTPS and SSL.
Related pages
Advanced notes
Some hosting providers need both a DNS change and a domain confirmation inside the app settings. Do not stop after only one of those two steps.