Cloudflare — DNS Map
Complete DNS record mapping for all EchoHuman and hosted domains.
echohuman.org Records
| Type | Name | Value | Proxied | TTL | Purpose |
|---|---|---|---|---|---|
| A | crm | 65.108.159.249 | Yes | Auto | EchoHuman Twenty CRM |
| A | analytics | 65.108.159.249 | Yes | Auto | Matomo Analytics |
| A | docsaurus | 65.108.159.249 | Yes | Auto | Docusaurus documentation |
lifehousestroud.org.uk Records
| Type | Name | Value | Proxied | TTL | Purpose |
|---|---|---|---|---|---|
| A | crm | 65.108.159.249 | Yes | Auto | Lifehouse Twenty CRM |
Record Routing
All A records point to Helsinki2 public IP 65.108.159.249, which routes to CT101 Caddy reverse proxy.
CT101 Caddy then routes by hostname to:
crm.echohuman.org→ VM700:7010 (EchoHuman Twenty)analytics.echohuman.org→ VM700:7020 (Matomo)docsaurus.echohuman.org→ VM700:7030 (Docusaurus)crm.lifehousestroud.org.uk→ VM700:3000 (Lifehouse Twenty)
Notes
- All records are Cloudflare-proxied (orange cloud)
- TTL is automatic when proxy is enabled
- No CNAME records needed — all use A records
- Cloudflare handles certificate provisioning automatically
Adding a DNS Record
- Log into Cloudflare dashboard
- Select domain
- Go to DNS tab
- Click "Add record"
- Type: A
- Name: subdomain (e.g., "newservice")
- IPv4 address: 65.108.159.249
- Proxy status: Proxied (orange cloud)
- Save
- Add route in CT101 Caddyfile
- Reload Caddy:
pct exec 101 -- systemctl reload caddy - Test:
curl -I https://newservice.echohuman.org - Update this documentation