Skip to content

Clarify DNS record names for custom domains#1155

Closed
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-relative-dns-record-names
Closed

Clarify DNS record names for custom domains#1155
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-relative-dns-record-names

Conversation

@radiantjade
Copy link
Copy Markdown
Contributor

Summary

  • Clarifies that some DNS providers ask for record names relative to the zone root.
  • Shows how a Railway custom domain like www.example.com can map to www for the CNAME name and _railway-verify.www for the TXT name in those DNS UIs.
  • Keeps the existing instruction that Railway-provided record values should not be changed.

Related Central Station reports:

Verification

  • git diff --check
  • pnpm exec content-collections build

Some DNS providers ask users to enter hostnames relative to the zone root, which makes Railway's dashboard examples look inconsistent for subdomains. The docs now explain how values like @ and _railway-verify map when the Railway custom domain is itself a subdomain such as www.example.com.

Constraint: Station bounty comments are currently blocked, so this uses a reviewable docs PR rather than another Central Station reply.
Rejected: Provider-specific GoDaddy-only instructions | broader wording applies to multiple DNS UIs without overfitting the docs.
Confidence: medium
Scope-risk: narrow
Tested: git diff --check; pnpm exec content-collections build
Not-tested: Full pnpm build
@radiantjade radiantjade force-pushed the clarify-relative-dns-record-names branch from 8ed9f06 to 6bbfb2f Compare May 15, 2026 07:38
@brody192 brody192 closed this May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants