domain
This skill should be used when the user wants to add a domain, generate a railway domain, check current domains, get the URL for a service, or remove a domain.
When & Why to Use This Skill
This Claude skill provides comprehensive domain management for Railway services, enabling users to generate automatic Railway domains, configure custom domains with instant DNS record generation, and manage service networking configurations through simple natural language commands. It streamlines the DevOps workflow by bridging the gap between service deployment and public accessibility.
Use Cases
- Instant Public Access: Automatically generate a '.up.railway.app' domain for a newly deployed service to quickly share or test the application.
- Custom Domain Integration: Add professional domains (e.g., example.com) to Railway services and retrieve the specific CNAME or A records required for DNS provider configuration.
- Networking Audits: Query and list all active domains and URLs associated with a specific environment or service to verify deployment status.
- Infrastructure Maintenance: Efficiently remove obsolete or unused domains from service configurations to keep the cloud environment clean and organized.
| name | domain |
|---|---|
| description | This skill should be used when the user wants to add a domain, generate a railway domain, check current domains, get the URL for a service, or remove a domain. |
| allowed-tools | Bash(railway:*) |
Domain Management
Add, view, or remove domains for Railway services.
When to Use
- User asks to "add a domain", "generate a domain", "get a URL"
- User wants to add a custom domain
- User asks "what's the URL for my service"
- User wants to remove a domain
Add Railway Domain
Generate a railway-provided domain (max 1 per service):
railway domain --json
For a specific service:
railway domain --json --service backend
Response
Returns the generated domain URL. Service must have a deployment.
Add Custom Domain
railway domain example.com --json
Response
Returns required DNS records:
{
"domain": "example.com",
"dnsRecords": [
{ "type": "CNAME", "host": "@", "value": "..." }
]
}
Tell user to add these records to their DNS provider.
Read Current Domains
Use environment skill to see configured domains, or query directly:
query domains($envId: String!) {
environment(id: $envId) {
config(decryptVariables: false)
}
}
Domains are in config.services.<serviceId>.networking:
serviceDomains- Railway-provided domainscustomDomains- User-provided domains
Remove Domain
Use environment skill to remove domains:
Remove custom domain
{
"services": {
"<serviceId>": {
"networking": {
"customDomains": { "<domainId>": null }
}
}
}
}
Remove railway domain
{
"services": {
"<serviceId>": {
"networking": {
"serviceDomains": { "<domainId>": null }
}
}
}
}
Then use environment skill to apply and commit the change.
CLI Options
| Flag | Description |
|---|---|
[DOMAIN] |
Custom domain to add (omit for railway domain) |
-p, --port <PORT> |
Port to connect |
-s, --service <NAME> |
Target service (defaults to linked) |
--json |
JSON output |
Composability
- Read domains: Use
environmentskill - Remove domains: Use
environmentskill - Apply removal: Use
environmentskill - Check service: Use
serviceskill
Error Handling
No Service Linked
No service linked. Use --service flag or run `railway service` to select one.
Domain Already Exists
Service already has a railway-provided domain. Maximum 1 per service.
No Deployment
Service has no deployment. Deploy first with `railway up`.
Invalid Domain
Invalid domain format. Use a valid domain like "example.com" or "api.example.com".