Skip to main content

DNS Management

DNS for jettaintelligence.com is managed through AWS Route53. MCPammer provides tools to create, list, and delete A records.

Domain Structure​

jettaintelligence.com
├── status.jettaintelligence.com      # Status page
├── hq.jettaintelligence.com          # Coolify dashboard
├── artemis.jettaintelligence.com     # LLM proxy
├── myapp.jettaintelligence.com       # Your apps
└── api.myapp.jettaintelligence.com   # Nested subdomains

Default Configuration​

  • Server IP: 80.209.241.157 (Coolify server)
  • TTL: 300 seconds (5 minutes)
  • Record Type: A record

Common Operations​

List All Records​

mcpammer dns list

Shows all A records with subdomain, FQDN, and IP.

Add a Record​

# Points to Coolify server by default
mcpammer dns add myapp

# Custom IP
mcpammer dns add myapp --ip 192.168.1.100

Creates: myapp.jettaintelligence.com → 80.209.241.157

Check if Record Exists​

mcpammer dns exists myapp

Returns true/false.

Delete a Record​

mcpammer dns delete myapp

Workflow: New Service​

  1. Create DNS record

    mcpammer dns add myservice

  2. Verify propagation (wait up to 5 minutes)

    nslookup myservice.jettaintelligence.com

  3. Configure in Coolify

    • Set domain to myservice.jettaintelligence.com
    • SSL certificate auto-generated

Nested Subdomains​

For API or versioned endpoints:

# api.myapp.jettaintelligence.com
mcpammer dns add api.myapp

# v2.api.myapp.jettaintelligence.com
mcpammer dns add v2.api.myapp

DNS Propagation​

  • Route53 changes typically propagate in 1-5 minutes
  • TTL is 300 seconds, so cached records expire in 5 minutes
  • Use nslookup or dig to verify:
nslookup myapp.jettaintelligence.com
dig myapp.jettaintelligence.com A

Troubleshooting​

Record not resolving​

  • Wait 5 minutes for propagation
  • Verify record exists: mcpammer dns exists myapp
  • Check for typos in subdomain

Wrong IP​

  • Delete and recreate: 
    mcpammer dns delete myapp
    mcpammer dns add myapp --ip CORRECT_IP

SSL certificate not working​

  • DNS must resolve before Coolify can get certificate
  • Check Coolify logs for Let's Encrypt errors
  • Ensure domain in Coolify matches DNS exactly

Best Practices​

  1. Create DNS before deploying - SSL needs DNS to work
  2. Use descriptive names - api-v2 not app2
  3. Clean up unused records - Delete when decommissioning
  4. Document custom IPs - If not using default Coolify server