a month ago
Cannot add DNS records to Railway-managed domain
Domain
- Domain: .com (purchased through Railway)
- DNS management: Railway ("Railway is managing DNS for this domain")
- Nameservers: the four ns*.name.com nameservers Railway assigned
Error
When adding any CNAME record in the DNS Records UI (workspace -> domains -> DNS Records), I get:
Failed to save DNS record
Problem processing request
This occurs regardless of the record's Type, Name, Target, or TTL.
What I'm trying to add
A third-party service requires these CNAME records on subdomains of my domain:
- CNAME clerk -> frontend-api.clerk.services (TTL 300)
- CNAME accounts -> accounts.clerk.services (TTL 300)
- CNAME clkmail -> mail..clerk.services (TTL 300)
- CNAME clk._domainkey -> dkim1..clerk.services (TTL 300)
- CNAME clk2._domainkey -> dkim2..clerk.services (TTL 300)
What I've tried / ruled out
-
Not a root-conflict issue. I initially tried @ as the Name and got a separate, sensible warning ("A record at this host already points to a Railway service"). I corrected this and used subdomain labels only (clerk, accounts, etc.). The "Problem processing request" error persists on plain subdomains that have no existing records.
-
Not an underscore issue. The error reproduces on clerk and accounts (plain labels with no special characters), not only on the _domainkey records.
-
Confirmed the subdomains are empty. Querying the authoritative nameservers directly returns no records for any of these subdomains, so there is no conflict to resolve:
dig +short CNAME clerk..com @ (empty)
dig +short CNAME accounts..com @ (empty)
-
Existing root records are healthy and should be preserved:
- ANAME @ -> .up.railway.app
- TXT _railway-verify ->
Impact
Production authentication is blocked. My production publishable key for the third-party service resolves to a subdomain of my domain (e.g. clerk..com) that is currently unresolvable, so sign-in is broken until at least that CNAME is in place.
Expected behavior
Adding a CNAME record with a valid Type, Name, Target, and TTL should succeed without error, and the record should appear in the DNS Records list and propagate to the authoritative nameservers.
Request
Could Railway add these records on the backend, or identify what's causing the validator to reject them? Happy to share the actual domain/workspace ID privately if a Railway team member can DM me.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The DNS records table for Railway-purchased domains supports adding CNAME, MX, TXT, and other record types directly from your domain's management page, and the records you're describing (CNAME on plain subdomain labels like clerk, accounts, etc.) are standard entries the feature should accept. The "Problem processing request" error on these entries is not expected behavior. Please reply here if you'd like to share your domain name so we can look at what's happening on that specific zone.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago