DNS records we want to add — a triage list, nothing here blocks a live service. immune already has a public home on Hugging Face (szlholdings-immune.hf.space), so its subdomain is a nice-to-have, on hold for now.
| Host / record | Type | Target | TTL | Status | Notes / action |
|---|---|---|---|---|---|
immune.a-11-oy.com |
A | 167.233.50.75 |
300 | PENDING BLOCKED | Box side is staged: nginx vhost added (nginx -t OK), container listening, TLS to be issued by certbot after the A-record resolves. Add the A-record at the registrar for a-11-oy.com. Registrar API is disabled at the account level (Namecheap error 1011102), so it must be added by hand in the registrar dashboard — see step list below. No outage in the meantime: immune is served on Hugging Face. |
Known infrastructure gaps that may want DNS. Listed as candidates only — confirm whether we actually want each before adding.
| Host / record | Type | Target | Status | Notes |
|---|---|---|---|---|
killinchu.net |
registration + DNS | — | CANDIDATE BLOCKED | Domain registration / DNS is founder-gated (registrar account). Decide whether to register and where to point it. |
companion.alloyszlholdings.com |
A | 5.161.81.107 |
CANDIDATE | Companion chatbox runs on the secondary box (5.161.81.107, a different host than a11oy) but has no public A-record yet. Add only if we want the chatbox on a public subdomain. |
manifesto.alloyszlholdings.com |
A | 5.161.81.107 |
CANDIDATE | Manifesto chatbox, same box as above. Same decision as the companion chatbox. |
immune), Value = the target IP, TTL = Automatic (or 300).dig immune.a-11-oy.com +short (should return the target IP).certbot --nginx -d immune.a-11-oy.com.The registrar API is disabled on this account (Namecheap returns error 1011102, "API Key is invalid or API access has not been enabled"), so these records can't be added programmatically right now — they must be added by hand in the dashboard, or API access re-enabled in the registrar account settings.
dig <name> +short before relying on it.