Railway

"records": { "CNAME": "abcd12.up.railway.app" }

Railway generates a unique *.up.railway.app CNAME target for each custom domain in its dashboard, so abcd12.up.railway.app above is a stand-in. Copy the exact value Railway shows you, not this one.

Two ways to apply this. The quickest is runs-at.dev/manage: sign in, pick the record type, paste the value, save. It writes the same commit to the registry and DNS follows within seconds. The steps below do it by pull request instead, which is what you want if you would rather review the change first. Either way handles subdomains entries.

1. In the Railway dashboard: your service → Settings → Networking → Custom Domain → enter you.runs-at.dev. Railway shows you the CNAME target to use.
2. Fork the registry and edit domains/you.json, setting CNAME to the exact value Railway gave you.
3. Open a pull request. Once merged, the CNAME is synced to DNS automatically.

Railway also asks for a TXT record to verify domain ownership, alongside the CNAME. Our schema will not accept both at once: CNAME cannot coexist with TXT at the same name, since a DNS name with a CNAME cannot carry any other record type. If Railway shows the TXT record at the same hostname as the CNAME (you.runs-at.dev itself), there is no way to add it here, so skip it and add only the CNAME above. If Railway's dashboard keeps the domain unverified without the TXT record, this is the limit of what this registry can express for Railway: contact Railway support about verifying without it, or host on a provider that only needs a CNAME.

If Railway instead shows the TXT record at a different hostname (a prefixed subdomain, for example), add it under subdomains at that label instead, since a subdomain entry and the root records object don't share the CNAME-exclusivity rule with each other.

Networking → Custom Domain shows the domain as active once Railway has confirmed it. Visiting https://you.runs-at.dev should then serve the service.