Deploy and Manage › Custom Domains
Custom Domains
-
Overview
This guide explains how to connect a custom domain to your Emergent deployment. The process includes adding DNS records to verify domain ownership and route traffic to your application. -
Prerequisites
- An active Emergent deployment
- Access to your domain’s DNS management panel
- Domain registrar login credentials (GoDaddy, Namecheap, Cloudflare, etc.)
- Step-by-Step Process
3.1 Initiate Custom Domain Setup
- Go to the Deployments section in Emergent
- Locate the Custom Domain section
- Click the "Link Domain" button
- Enter your domain name (for example: emergent1.feelingcoding.xyz)
- Choose "Auto-Link" or "Link Manually"
3.2 Manual Setup
If you choose to proceed manually, add the following DNS records.
Required A records
Record 1
- Type: A
- Name: www
- Value: 162.159.142.117
- TTL: 3600
Record 2
- Type: A
- Name: www
- Value: 172.66.2.113
- TTL: 3600
CNAME record
- Type: CNAME
- Name: www
- Value: @
- TTL: 3600
3.3 Auto-Link Setup
If you choose Auto-Link:
- A pop-up will indicate that Emergent uses Entri for domain configuration
- Click Continue
- Click Authorize with your service provider
- You will be redirected to your domain provider’s login page
- Enter your credentials
- Wait briefly and confirm the status shows Verified
3.4 Add DNS Records to Your Provider
Cloudflare
- Log in to the Cloudflare dashboard
- Select your domain
- Go to DNS → Records
- Click Add record
- Select A as the record type
- Enter the subdomain name (for example: emergent1)
- Add the following IP addresses:
- 162.159.142.117
- 172.66.2.113
- Set Proxy status to DNS only
- Save the record
GoDaddy
- Log in to your GoDaddy account
- Go to My Products → DNS
- Find your domain and click Manage
- Click Add in the Records section
- Select A as the record type
- Enter the host (subdomain name)
- Enter the IP address
- Save the record
Namecheap
- Log in to your Namecheap account
- Open Domain List
- Click Manage next to your domain
- Go to the Advanced DNS tab
- Click Add New Record
- Select A Record
- Enter the host and IP address
- Save the record
3.5 Verify Domain Ownership
- Return to Emergent after adding DNS records
- Click Refresh Status
- Wait 5–15 minutes for verification
- Once verified, the status will appear as Verified
3.6 Complete Setup
- Your custom domain is now active
- You can access your application using the custom domain
- The domain will automatically point to your live deployment
- Important Notes
DNS Propagation
- DNS changes usually propagate within 5–15 minutes
- In some cases, global propagation may take up to 24 hours
- Online DNS checker tools can be used to confirm propagation
Critical Requirements
- Ensure two A records point to your domain
- Do not add multiple IP addresses for the same subdomain
- Remove any conflicting DNS records before adding Emergent records
- Incorrect or duplicate records may cause routing issues
- Troubleshooting
Domain Not Verifying
- Recheck DNS record values
- Ensure TTL is set to 300 seconds or lower
- Wait 15–30 minutes and try again
- Use DNS lookup tools to confirm records exist
SSL Certificate Issues
- SSL certificates are provisioned automatically
- Allow 5–10 minutes after verification
- Contact support if the issue persists
Domain Not Loading
- Confirm A records are correctly configured
- Ensure no conflicting A records exist
- Verify the domain status in Emergent
- Try opening the site in incognito or private mode
- Security Best Practices
- Keep DNS records minimal and relevant
- Monitor domain verification status regularly
- Use a reliable DNS provider
- Enable domain lock to prevent unauthorized transfers
- Support
If you face issues during setup:
- Recheck DNS configuration
- Allow time for DNS propagation
- Review the troubleshooting section
When contacting Emergent support, share:
- Your domain name
- DNS configuration screenshots
- Any error messages
Deployment Time
- Custom domain setup usually completes within 5–15 minutes after DNS propagation
Reminder
- Always ensure two IP addresses point to your domain to avoid routing conflicts
For help or questions, contact
support@emergent.sh
