Custom Domains
Connect your own domain to your Galaxy app. CNAME records, A records, ALIAS records, and automatic SSL certificates. Your app, your brand.
Why Custom Domains?
Your app deserves a real domain. Instead of myapp.meteorapp.com or myapp.galaxycloud.app, use app.yourcompany.com or yourcompany.com. Same app, professional branding.
Galaxy makes this simple. Point your DNS at us, add the domain in your dashboard, and we handle SSL certificates automatically. No manual certificate management. No renewal headaches.
Automatic SSL
Every custom domain gets a free Let's Encrypt certificate. Galaxy provisions it automatically and renews it before expiration. HTTPS just works.
Choose Your Setup Method
Three ways to connect your domain. Pick the one that fits your situation.
CNAME Record (Recommended)
Best for subdomains like www.yoursite.com or app.yoursite.com. Works with virtually all DNS providers. Simple and reliable.
A Record
For root domains when your DNS provider doesn't support ALIAS. Points directly to an IP address. Requires a dedicated IP from Galaxy.
ALIAS Record
For root domains with supporting DNS providers. No IP management needed. Best of both worlds.
Not sure which to pick? Use CNAME for subdomains (recommended) or ALIAS for root domains if your provider supports it. A records are the fallback when nothing else works.
Method 1: CNAME Records (Recommended)
CNAME is the simplest and most reliable approach. It works for subdomains like www.yoursite.com, app.yoursite.com, or dashboard.yoursite.com.
Subdomain Only
CNAME records can't be used for root domains (like yoursite.com without www). For root domains, use ALIAS or A records instead.
Galaxy Ingress Endpoints
Point your CNAME to the ingress endpoint for your app's region:
| Region | Ingress Endpoint |
|---|---|
| US East | username.us-east-1.galaxy-ingress.meteor.com |
| EU West | username.eu-west-1.galaxy-ingress.meteor.com |
| Asia Pacific | username.ap-southeast-2.galaxy-ingress.meteor.com |
Replace username with your Galaxy username. For example, if your username is acme-corp, your US East endpoint would be acme-corp.us-east-1.galaxy-ingress.meteor.com.
Step-by-Step Setup
Choose Your Subdomain
Decide which subdomain you want to use. Common patterns include www.yoursite.com for your main app or app.yoursite.com for a dedicated app subdomain.
Make sure this matches the hostname you'll add in Galaxy.
Add the CNAME Record
Log into your DNS provider (GoDaddy, Cloudflare, Namecheap, Route 53, wherever you manage DNS) and create a new CNAME record.
Example for www subdomain:
- Name/Host:
www - Type:
CNAME - Value/Target:
username.us-east-1.galaxy-ingress.meteor.com(replaceusernamewith your Galaxy username, use your region's endpoint) - TTL: 300 seconds (or your provider's default)
Save the record.
Wait for DNS Propagation
DNS changes take time to spread across the internet. Usually 30 minutes to 2 hours, sometimes up to 24 hours in rare cases.
Check propagation with this command:
dig www.yoursite.comYou should see a CNAME pointing to the Galaxy ingress endpoint.
Add the Domain in Galaxy
Open your app in the Galaxy dashboard. Go to Settings and find the Domain Management section. Click Add New Domain and enter your full domain (like www.yoursite.com).
Galaxy verifies DNS is pointing correctly.
Enable HTTPS
Once the domain is added, Galaxy automatically provisions an SSL certificate (usually takes a few minutes).
Enable Force HTTPS to redirect all HTTP traffic to HTTPS. Your users always get a secure connection.
That's it. Your custom domain is live with automatic SSL.
Method 2: A Records (Direct IP)
Use A records when you need a root domain and your DNS provider doesn't support ALIAS records. This method points your domain directly to an IP address.
Dedicated IP Required
A record setup requires a dedicated IP address from Galaxy. You'll find this in your app's Domains section.
Setup Process
Get Your Dedicated IP
Open your app in the Galaxy dashboard. Navigate to Settings and look at the Domains & HTTPS section. Galaxy displays a dedicated IP address for your application.
Copy this IP address.
Create the A Record
In your DNS provider, create an A record for your root domain.
Example:
- Name/Host:
@(or leave blank, depends on provider) - Type:
A - Value: Your dedicated IP from Galaxy
- TTL: 300 seconds
Add the Domain in Galaxy
After DNS propagation (30 minutes to a few hours), return to your Galaxy dashboard. Go to Settings and click Add New Domain. Enter your root domain (like yoursite.com).
Generate SSL Certificate
Click Generate Certificate to activate HTTPS. Galaxy provisions a Let's Encrypt certificate for your root domain.
Enable automatic HTTP to HTTPS redirection for best security.
Method 3: ALIAS Records (Root Domain)
ALIAS records (sometimes called ANAME) give you root domain hosting without managing IP addresses. Your DNS provider handles the translation behind the scenes.
Check Provider Support
Not all DNS providers support ALIAS records. These providers work well:
- Cloudflare: Uses "CNAME flattening" which works the same way
- AWS Route 53: Full ALIAS record support
- DNSimple: Comprehensive ALIAS functionality
- NS1: ALIAS record support included
If your provider isn't listed, check their documentation for ALIAS or ANAME support.
Setup Process
Create the ALIAS Record
In your DNS provider, create an ALIAS record for your root domain.
Example:
- Name/Host:
@(or leave blank) - Type:
ALIASorANAME - Value:
username.galaxy-ingress.meteor.com(replaceusernamewith your Galaxy username)
Set Up WWW Redirect
Since you're hosting on the root domain, set up a redirect so www.yoursite.com goes to yoursite.com. Most DNS providers offer URL forwarding for this.
Alternatively, add a CNAME for www pointing to Galaxy and configure both domains in your app.
Add Domain in Galaxy
Add your root domain in the Galaxy dashboard under Settings. Galaxy provisions SSL automatically.
Free Galaxy Subdomains
Don't have a custom domain yet? No problem. Galaxy provides free subdomains for your app. The format depends on your app type.
Meteor apps get a free subdomain on the meteorapp.com domain:
| Region | Subdomain Format |
|---|---|
| US East | yourapp.meteorapp.com |
| EU West | yourapp.eu.meteorapp.com |
| Asia Pacific | yourapp.au.meteorapp.com |
You choose your app name during deployment. If it's available, it's yours immediately.
Web Apps (Node.js, Python, AdonisJS) get a free subdomain on the sandbox.galaxycloud.app domain:
| Region | Subdomain Format |
|---|---|
| All Regions | yourapp.sandbox.galaxycloud.app |
You choose your app name during deployment. Galaxy handles regional routing automatically.
All free subdomains come with SSL enabled by default. No DNS configuration needed. Just deploy your app and you're live immediately.
Start Free, Add Custom Later
Use a Galaxy subdomain to get started quickly. Add your custom domain whenever you're ready. Both can work simultaneously on paid plans.
SSL Certificates
Galaxy handles SSL automatically. Here's what happens behind the scenes.
Automatic Provisioning
When you add a domain, Galaxy requests a Let's Encrypt certificate. This typically completes within a few minutes. If DNS isn't pointing correctly yet, Galaxy retries until it works.
Automatic Renewal
Certificates expire after 90 days. Galaxy renews them automatically before expiration. You don't need to track renewal dates or manually update anything.
Custom Certificates
Prefer using your own certificate (commercial CA, wildcard, or specific compliance requirements)? You can upload custom SSL certificates in the Domains section of your app settings.
WWW vs Non-WWW
Decide which format is your canonical URL, then redirect the other to it.
Primary: www.yoursite.com
- Set up CNAME for
wwwpointing to Galaxy - Set up root domain redirect to
www.yoursite.com - Add
www.yoursite.comas your domain in Galaxy
Most DNS providers offer URL forwarding for the root domain redirect.
Primary: yoursite.com
- Set up ALIAS or A record for root domain
- Set up CNAME for
wwwpointing to Galaxy (or redirect www to root) - Add
yoursite.comas your domain in Galaxy - Optionally add
www.yoursite.comas an additional domain
Both domains can work, or you can redirect www to the root.
Consistency matters. Pick one and stick with it. Search engines treat www and non-www as separate sites, so consolidating helps SEO.
Verifying Your DNS
After making changes, verify everything is working correctly.
Check DNS Records
# Check CNAME records
dig www.yoursite.com
# Check A records
dig yoursite.com
# Check from Google's DNS (bypasses local caching)
dig @8.8.8.8 yoursite.comWhat to Look For
CNAME setup: You should see a CNAME record pointing to the Galaxy ingress endpoint.
A record setup: You should see an A record with your dedicated IP address.
ALIAS setup: You should see A records (the ALIAS gets resolved to IP addresses by your DNS provider).
Troubleshooting
AWS Route 53 Advanced Setup
Using AWS for your infrastructure? Route 53 provides advanced DNS features like geographic routing, health checks, and tight AWS integration.
For comprehensive AWS Route 53 documentation, see the official AWS Route 53 Developer Guide.
The short version: create a hosted zone for your domain, update your registrar's nameservers to Route 53, then create ALIAS records pointing to Galaxy ingress endpoints.