domain_skill

This skill helps you add, view, or remove Railway domains, retrieve service URLs, and generate custom or railway domains efficiently.
  • Shell
  • Official

79

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill railwayapp/railway-skills --skill domain

  • SKILL.md2.7 KB

Overview

This skill manages domains for Railway services: add a Railway-provided domain, add a custom domain, list configured domains, get a service URL, or remove a domain. It ties into Railway environments and services to return DNS requirements, enforce limits, and apply domain removals.

How this skill works

Generating a Railway domain or adding a custom domain runs the domain command and returns either a generated URL or required DNS records to configure at your DNS provider. Reading and removing domains is done by inspecting and updating the environment configuration under services.<serviceId>.networking, then applying the change via the environment workflow. The skill validates service linkage, deployment presence, and domain format.

When to use it

  • Add a Railway-provided domain for a deployed service
  • Add a custom domain and get required DNS records
  • Ask "what's the URL for my service" or request the service URL
  • List current domains configured for an environment or service
  • Remove a custom or Railway-provided domain from a service

Best practices

  • Ensure the target service has a deployment before generating a Railway domain
  • Provide --service when no service is linked to avoid ambiguity
  • Copy all returned DNS records exactly into your DNS provider and wait for propagation
  • Use the environment skill to read current config and to apply/remove domains atomically
  • Respect the limit of one Railway-provided domain per service

Example use cases

  • Generate a Railway domain for the backend service to share a quick staging URL
  • Add example.com as a custom domain and return CNAME/A records for DNS setup
  • Check configured domains in the environment to audit routing
  • Remove an old custom domain from a service by updating networking.customDomains
  • Get the canonical URL for a service to include in documentation or CI tests

FAQ

Use the --service flag with the service name or run railway service to link a service before adding a domain.

Why can't I add another Railway domain?

Each service can have a maximum of one Railway-provided domain; remove the existing railway domain first if you need a new one.

What DNS records will I receive for a custom domain?

The command returns a JSON block listing DNS records (CNAME/A) and host values you must add at your DNS provider.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational