Railway Project Domain Not Resolving (DNS_PROBE_FINISHED_BAD_CONFIG) — App Running, Logs OK
rameeskv0
FREEOP
10 months ago
Hi Railway Team,
I’m experiencing a DNS issue with my project:
- Project name: lunch_app
- Old domain:lunchapp-production.up.railway.app
- New domain (after creating a new project):lunchapp-production-7be5.up.railway.app
- Internal domain: lunch_app.railway.internal
- Port: 8080 (Metal Edge)
Problem:
- The app is running and logs are showing activity (including Slack event webhooks).
- However, the public domain(s) do not resolve from anywhere (tested with curl, nslookup, dig).
- Error: DNS_PROBE_FINISHED_BAD_CONFIG and server can't find ...: REFUSED
- This happens even after creating a brand new Railway project from the same repo.
What I’ve tried:
- Redeploying the project
- Creating a new project (new domain)
- Waiting for DNS propagation
Request:
- Please investigate the DNS/Metal Edge configuration for my project.
- Is there a known issue with new domains not resolving?
- Is there a workaround or can you force a DNS refresh?
3 Replies
chandrika
EMPLOYEE
10 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open chandrika • 10 months ago
clashing
FREE
10 months ago
Thanks for pointing out that Railway sometimes expects to use the injected PORT variable
clashing
FREE
10 months ago
Are you using Custom Domains, rameeskv0?
parag7823
HOBBY
10 months ago
Same issue I am facing.