DNS & Subdomains pending records

A running list of the DNS records we want to add. Nothing here is blocking a live service — it is a triage list to work through. immune already has a public home on Hugging Face (szlholdings-immune.hf.space), so the subdomain is a nice-to-have that is on hold until the trip is over.

PENDING staged / ready, record not yet added BLOCKED needs founder / registrar action CANDIDATE unconfirmed — confirm when back DONE record live

1 · Pending records (confirmed)

Host / recordTypeTargetTTLStatusNotes / action
immune.a11oy.net 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 a11oy.net. 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.

2 · Backlog (confirm when back)

Known infrastructure gaps that may want DNS. Listed as candidates only — confirm whether we actually want each before adding.

Host / recordTypeTargetStatusNotes
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.

3 · How to add a record

  1. Sign in to the registrar that holds the domain (a11oy.net is on Namecheap).
  2. Open Domain List → Manage → Advanced DNS.
  3. Add a new record: Type = A, Host = the left-most label (e.g. immune), Value = the target IP, TTL = Automatic (or 300).
  4. Save. Allow a few minutes to propagate, then verify with dig immune.a11oy.net +short (should return the target IP).
  5. Once it resolves, issue TLS on the box: certbot --nginx -d immune.a11oy.net.

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.

Static infrastructure roadmap · no live data · Doctrine v11 · last updated 2026-06-16. Verify any record live with dig <name> +short before relying on it.