Custom Local Domains

DAMP automatically creates memorable local domains for each project and handles all the complex DNS and SSL configuration. Access your projects with professional URLs like my-blog.local instead of confusing localhost ports.

Why Custom Domains?

Problems with Port-Based Development

Traditional development often uses ports for different projects:

• localhost:8000 - Which project is this?
• localhost:3000 - Frontend or backend?
• localhost:8080 - Database admin or web app?
• Port conflicts when multiple projects run
• Hard to remember what’s running where
• No SSL support with simple port forwarding

DAMP’s Domain Solution

• ✅ Memorable URLs - my-blog.local, store.local
• ✅ Automatic SSL - All domains get HTTPS certificates
• ✅ No port confusion - Each project has its own domain
• ✅ Professional development - URLs match production patterns

Automatic Generation

Domains generated from project names:

• my-blog → my-blog.local
• e-commerce-store → e-commerce-store.local
• company-api → company-api.local
• Clean, predictable patterns

DNS Resolution

Hosts file entry for local domains:

• DAMP adds a record to your system’s hosts file
• Maps <project-name>.local to your local machine
• Works in all browsers
• No DNS proxy or wildcard subdomain support

SSL Integration

Every domain gets SSL certificates:

• Automatic generation for new domains
• Wildcard certificates for subdomains
• Browser trust via DAMP CA
• HTTPS by default for secure development

How DAMP Domains Work

Automatic Domain Creation

When you create a new project:

1. Project Name Analysis

   DAMP converts your project name to a domain:

   • My Blog → my-blog.local
   • E-Commerce Store → e-commerce-store.local
   • Company API v2 → company-api-v2.local

2. Hosts File Entry

   DAMP adds a record to your system’s hosts file:

   • Maps <project-name>.local to your local machine

3. SSL Certificate Generation

   Automatic SSL setup for the domain:

   • Generates domain-specific certificate
   • Includes wildcard for subdomains (*.my-blog.local)
   • Configures Nginx for HTTPS

Browser Request: https://my-blog.local
        ↓
Host System (Windows/macOS/Linux)
   ↓
Hosts File Record (maps my-blog.local to 127.0.0.1)
   ↓
Project Application (PHP/Node.js/etc.)

Troubleshooting Domains

Common Domain Issues

Domain Not Resolving

Symptoms: my-blog.local doesn’t load in browser

Solutions:

1. Check Hosts file for correct entry
2. Verify domain in project settings
3. Restart DAMP network services
4. Clear browser DNS cache
5. Test with different browser

Debugging Commands

SSL Testing

# Test SSL certificate
openssl s_client -connect my-blog.local:443 -servername my-blog.local

# Check certificate details
curl -vI https://my-blog.local

# Test certificate chain
ssl-cert-check -c my-blog.local:443

Network Connectivity

# Test network connectivity
ping my-blog.local
telnet my-blog.local 80
telnet my-blog.local 443

# Check DAMP proxy status
curl -I http://127.0.0.1:80 -H "Host: my-blog.local"

Domain Pro Tips

• Test domains in multiple browsers to ensure compatibility
• Keep domain names short for easier typing and memory
• Use HTTPS everywhere to match production environment

Custom domains in DAMP make development feel professional and organized, eliminating the confusion of port-based development while providing production-like URLs for testing and demonstration.