Point an existing domain at your Rocket.new app with automatic HTTPS - let Rocket configure DNS for supported registrars or add records manually.
Connect any domain you own to your Rocket app so it is reachable at your custom address with automatic HTTPS.If you do not own a domain yet, you can buy one directly through Rocket (paid plan required).
Connecting a custom domain requires a paid plan (Pro or above). You also need a Rocket task that has been deployed to the web and access to your domain provider account.
Rocket tries to configure DNS automatically by default. For supported providers, it logs into your domain account with one-time permission and updates the records for you. If automatic setup is not available for your provider or fails, you can fall back to the manual method where Rocket gives you the exact records to add yourself.
Rocket uses an automated flow to log in to your domain provider and configure DNS automatically with your permission. This works for supported providers.
1
Open the Production tab in the Launch panel
Click the Launch button in the top-right corner of your project, then click the Production tab.
Click the Production tab in the Launch panel
2
Select a version and enter your domain
Choose which version of your app to publish from the version dropdown. Once you select a version, type your domain in the Custom domain field (for example, example.com) and click Next.
Select a version from the dropdown
Once you publish on a version, you can only move forward to newer versions. To go back to an earlier version, you need to unpublish and publish again from that version.
Enter your domain and click Next
3
Set up the Production Environment
Rocket prompts you to configure your Production Environment. Click Setup now to add any required environment variables. If you have no environment variables to add, click Skip & continue.
Production Environment setup prompt
4
Add environment variables and click Done
Add your required environment variables in the Production environment settings, then click Done to continue.
Add environment variables and click Done
5
Continue with automatic setup
Rocket opens a popup explaining that it will configure your domain automatically. Click Continue.
Automatic setup popup, click Continue
6
Authorize with your domain provider
Rocket shows a login screen for your domain provider. Enter your credentials and click Continue to grant one-time permission to configure DNS.
Log in to authorize your domain provider
7
Confirm the DNS update
Your provider shows the existing DNS records and the new ones Rocket wants to add. Review them and click Okay, continue to approve the change.
Confirm the DNS records to update
8
Done
Your domain is confirmed as configured. Click Done. DNS propagation can take up to 48 hours, after which your app is live at your custom domain.
Domain configured successfully
Once live, the Launch panel shows your domain URL. You can click it to open your app.
Use this method if automatic setup is not available for your provider or did not complete successfully. Rocket shows you the exact DNS records and you add them directly in your domain provider’s dashboard.
1
Open the Production tab and select a version
Click the Launch button, select the Production tab, choose your version, enter your domain, and click Next. Complete the Production Environment step as described above.
2
Switch to manual setup
If automatic setup did not work or your provider is not supported, click Go to our manual setup on the automatic setup screen. Rocket shows you the exact DNS records to add.
Manual DNS records provided by Rocket
Remove any existing A and AAAA records for your domain before adding the new ones. Conflicting records will prevent your domain from connecting.
Copy each record (Type, Host Name, Required Value). In a new browser tab, open your domain provider’s DNS settings and add them exactly as shown.
3
Confirm you have added the records
Once you have added all records in your provider’s dashboard, click I have added all records above to my domain’s provider in Rocket. Rocket starts monitoring for the DNS changes.
You're all set
DNS propagation can take up to 48 hours. Once Rocket detects the records, your domain goes live automatically.
1
Open the More tab
Open your app in the Rocket mobile app and tap the More tab at the bottom of the screen.
More tab in the navigation bar
2
Select Launch on custom domain
In the settings modal, tap Launch on custom domain.
Project settings modal with Launch on custom domain option
3
Add your domain
Tap + Add domain, type the domain you own (for example, example.com), and tap Add Domain.Rocket adds the domain to your project and shows the DNS records you need.
Enter your domain
4
Update DNS settings at your domain provider
Copy the DNS records that Rocket shows you.
Copy your DNS records
Open your domain provider’s dashboard (you may need a web browser for this step) and add the records exactly as shown.What to add:
Root domains (e.g., example.com): Add two A records, one with host @ (root) and one with host www, both pointing to the IP address provided by Rocket.
Subdomains (e.g., app.example.com): Add one A record with the subdomain as the host (e.g., app), pointing to the IP address provided by Rocket.
5
Verify your domain
Return to the Rocket mobile app and tap Refresh next to your domain. The status shows Verification in process at first.When Rocket detects the correct DNS records, the status changes to Live. Your app is now accessible at your custom domain.
Verification status
DNS changes can take up to 48 hours to propagate. Your domain may not work immediately after setup.
If your domain is not connecting after 48 hours, you likely have conflicting DNS records.
1
Check your DNS records
Go to dnschecker.org, enter your domain, and select A as the record type.
2
Remove conflicting records
If you see multiple different IP addresses, log in to your domain provider’s dashboard and remove any A records that do not point to the IP address Rocket provided.
3
Wait for propagation
Wait up to 24 hours for the changes to propagate, then check the domain status in Rocket again.
Multiple A records with different IP addresses cause your domain to intermittently point to the wrong server. Keep only the Rocket IP address configured.
