Configure fulcrum.org on Bluehost — Dot Matrix Tutorial
Interactive step flow. This page includes a secure placeholder panel for Mainframe deployment credentials — replace placeholders locally and never commit secrets to source control.
Start
Start: Access Bluehost DNS Manager
Log in to Bluehost → Domains → DNS Zone Editor
1
Verify Nameservers
Ensure Bluehost is authoritative
ns1.Bluehost.com — server 1
ns2.Bluehost.com — server 2
2
Add A / Root records
A host: "" / @ → 173.254.31.123 (hosting)
A host: localhost → 127.0.0.1 (hosting)
3
Add service A records
A host: api → 45.76.22.150 (hosting)
A host: autodiscover → 173.254.31.123
A host: mail → 173.254.31.123
A host: webdisk → 173.254.31.123
4
Add CNAMEs and mail aliases
CNAME host: imap → mail.fulcrum.org
POP value: ""
SMTP value: ""
CNAME host: webmail → (blank)
CNAME host: www → www.fulcrum.org
5
Add FTP account
Create FTP user for fulcrum.org in Bluehost control panel (username, password, home directory)
6
Optional: ExternalDNS / cert-manager
Enable for automatic DNS and TLS provisioning
7
Verify and test
dig fulcrum.org +short
dig api.fulcrum.org +short
curl -v https://fulcrum.org/health
Trigger webhook test to https://fulcrum.org/webhook/fulcrum
Master nameservers
ns1.Bluehost.com (server 1)
ns2.Bluehost.com (server 2)
Records
Quick list
api A → 45.76.22.150
@ / root A → 173.254.31.123
autodiscover A → 173.254.31.123
localhost A → 127.0.0.1
mail A → 173.254.31.123
webdisk A → 173.254.31.123
imap CNAME → mail.fulcrum.org
webmail CNAME → (blank)
www CNAME → www.fulcrum.org
Mainframe
Mainframe Deployment Credentials (placeholders)
Fill these locally. Do not store secrets in this file in source control.
Security: these values are stored only in your browser's localStorage when you click Save. For CI/CD, inject credentials via your secrets manager (Vault, GitHub Secrets, Kubernetes Secret).