Your domain name is your digital real estate - your address on the internet. Let's explore everything you need to know about managing domains in Enhance.
Domain Basics
What is a Domain?
A domain name (like example.com) is the human-friendly address that points to your website. Behind the scenes, it translates to an IP address (like 192.168.1.1) that computers actually use.
Domain Structure
blog.example.com
│ │ │
│ │ └── TLD (Top-Level Domain)
│ └────────── SLD (Second-Level Domain)
└─────────────── Subdomain
Adding Domains to Enhance
Adding a New Domain
- Navigate to Websites or Domains
- Click + Add Domain or + Add Website
- Enter your domain name
- Choose setup options:
- Create new website
- Add as alias to existing site
- Add as subdomain
- Click Add
[SCREENSHOT: Add domain form with domain name input and setup options]
Domain Requirements
Before adding a domain:
- You must own or control the domain
- Domain must be registered with a registrar
- You'll need to update DNS to point to your server
After Adding a Domain
Enhance will display:
- Your server's IP address (for A records)
- Nameservers (if using Enhance DNS)
- Required DNS configuration
[SCREENSHOT: Post-domain setup showing required DNS records]
Pointing Your Domain to Enhance
Option 1: Update Nameservers
Point your domain's nameservers to Enhance:
- Log into your domain registrar
- Find nameserver settings
- Replace existing nameservers with Enhance nameservers:
ns1.yourhostingprovider.com
ns2.yourhostingprovider.com
- Save changes
Pros: Enhance manages all DNS for you
Cons: Can't use external DNS services
Option 2: Update A Records
Keep your current DNS and just point the domain:
- Log into your current DNS provider
- Update or create A records:
@ → Your server IP (e.g., 192.168.1.1)
www → Your server IP
- If using email, add MX records too
- Save changes
Pros: Flexibility, can use external DNS services
Cons: Must manage DNS separately
[SCREENSHOT: Example A record configuration at a registrar]
Managing Addon Domains
Addon domains let you host multiple separate websites on one account.
Adding an Addon Domain
- Go to Domains > Addon Domains
- Click + Add Addon Domain
- Enter the new domain
- Set the document root (where files will live)
- Create FTP account (optional)
- Click Add
[SCREENSHOT: Addon domain creation form]
Addon Domain Document Root
Each addon domain gets its own folder:
/home/user/
├── public_html/ ← Primary domain
├── addondomain1.com/ ← First addon
├── addondomain2.com/ ← Second addon
└── addondomain3.com/ ← Third addon
Domain Aliases (Parked Domains)
Domain aliases point multiple domains to the same website content.
Use Cases
- Owning multiple TLDs:
example.com, example.co.uk, example.net
- Common misspellings:
exmple.com
- With and without www:
www.example.com → example.com
Creating an Alias
- Go to Websites > Your Primary Domain
- Click Domain Aliases or Aliases
- Click + Add Alias
- Enter the alias domain
- Save
[SCREENSHOT: Domain alias configuration panel]
Redirect vs Alias
| Type |
What Happens |
URL Shows |
| Alias |
Same content, no redirect |
The alias URL |
| Redirect |
Forwards to primary domain |
Primary domain URL |
For SEO, redirects are usually better to avoid duplicate content.
Subdomains
Subdomains are prefixes to your main domain: blog.example.com, shop.example.com.
Creating Subdomains
- Go to Websites > Your Domain > Subdomains
- Click + Create Subdomain
- Enter the subdomain prefix (e.g.,
blog)
- Set document root:
- New folder:
/public_html/blog/
- Or existing folder
- Save
[SCREENSHOT: Subdomain creation form with prefix and document root fields]
Subdomain Ideas
| Subdomain |
Use Case |
www |
Traditional web prefix |
blog |
Separate blog installation |
shop |
E-commerce store |
app |
Web application |
mail |
Webmail access |
staging |
Test environment |
dev |
Development site |
api |
API endpoints |
Domain Redirects
Creating Redirects
- Go to Domains > Redirects
- Click + Add Redirect
- Configure:
- Source: Domain or path to redirect from
- Destination: Where to redirect to
- Type: 301 (permanent) or 302 (temporary)
- Save
[SCREENSHOT: Redirect configuration showing source, destination, and type options]
Redirect Types
| Type |
When to Use |
SEO Impact |
| 301 |
Permanent moves |
Transfers SEO value |
| 302 |
Temporary changes |
No SEO transfer |
Common Redirect Scenarios
Non-www to www:
example.com → www.example.com (301)
HTTP to HTTPS:
http://example.com → https://example.com (301)
Old page to new:
/old-page → /new-page (301)
Old domain to new:
olddomain.com/* → newdomain.com/* (301)
Wildcard Domains
Wildcard domains catch ALL subdomains:
*.example.com → Same destination
anything.example.com → Works!
random123.example.com → Also works!
Setting Up Wildcard
- Go to DNS management
- Add an A record:
- Name:
*
- Value: Your server IP
- Configure web server to handle wildcard
Use Cases
- Multi-tenant applications
- User subdomains (like
username.example.com)
- Development environments
- Catch-all for typos
Domain Transfer Checklist
Moving a domain to or from Enhance? Here's your checklist:
Before Transfer
- [ ] Domain must be unlocked at current registrar
- [ ] Obtain EPP/auth code from current registrar
- [ ] Domain must be older than 60 days
- [ ] Domain not expired (or recently renewed)
- [ ] Admin email on domain must be accessible
- [ ] Back up all DNS records
During Transfer
- [ ] Keep DNS records intact until transfer completes
- [ ] Monitor for approval emails
- [ ] Approve transfer request promptly
- [ ] Transfers typically take 5-7 days
After Transfer
- [ ] Verify DNS records are correct
- [ ] Update nameservers if needed
- [ ] Test website and email functionality
- [ ] Re-lock domain for security
Domain Security
Domain Locking
Keep your domain locked to prevent unauthorized transfers:
- Log into your registrar
- Find "Domain Lock" or "Transfer Lock"
- Ensure it's enabled
- Only unlock when intentionally transferring
WHOIS Privacy
Hide your personal information in public WHOIS records:
- Most registrars offer WHOIS privacy
- Enable it during or after registration
- Your info is replaced with proxy details
DNS Security Extensions (DNSSEC)
DNSSEC adds cryptographic verification to DNS:
- Check if your registrar supports DNSSEC
- Generate DS records in Enhance
- Add DS records at your registrar
- Verify with online DNSSEC checker
[SCREENSHOT: DNSSEC configuration panel]
Troubleshooting Domain Issues
"Domain Not Resolving"
- Check DNS records are correct
- Wait for propagation (up to 48 hours)
- Verify nameservers are set correctly
- Use
dig or nslookup to test
"Website Shows Wrong Content"
- Clear browser cache
- Check document root configuration
- Verify A record points to correct IP
- Check for conflicting aliases
"SSL Certificate Won't Issue"
- Verify A record is correct
- Wait for DNS propagation
- Check CAA records aren't blocking
- Ensure port 80 is accessible
"Email Not Working"
- Verify MX records are correct
- Check MX priority values
- Ensure mail server hostname resolves
- Wait for DNS propagation
Next Steps: Integrate with external services using our API Access Guide.