2 months ago
- Service is running but DNS domains (hireblind.up.railway.app, hireblind-production.up.railway.app) are not resolving
- Include: Project ID
c244d49b-9db9-4200-9cad-3516afcaafd1, Service ID2c959d80-5e9f-4762-8850-f03ec5727dc3
Pinned Solution
2 months ago
I can resolve those domains just fine on my machine. I'd try accessing them from a different machine or clearing your local DNS cache.
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open Railway • about 2 months ago
2 months ago
Service is running but the .up.railway.app subdomains aren't resolving ,this is on Railway's side, not yours. Those subdomains are fully Railway managed so there's nothing you can change to fix it directly.
Quick checks
Run dig hireblind-production.up.railway.app, if you get NXDOMAIN, Railway hasn't provisioned the subdomain yet. If it times out, it's provisioned but not routing.
Check the Networking section in your service settings and confirm the domain is actually enabled there, not just visible.
If the service was recently renamed or redeployed, the subdomain may have been regenerated and the old one orphaned.
If none of that helps
Contact Railway support with your project ID and service IDand ask them to check subdomain provisioning on their DNS layer.
2 months ago
I can resolve those domains just fine on my machine. I'd try accessing them from a different machine or clearing your local DNS cache.
Status changed to Solved 0x5b62656e5d • 16 days ago