2 months ago
Hi Railway Support,
I'm on the Pro plan ($20/mo) and my service (onfleet-roadie, project: SFNYC Middleware) cannot resolve DNS for api.onfleet.com. Other external APIs work fine from the same service — connect.roadie.com and api.burqup.com both resolve and connect without issues.
Diagnostics from inside the container:
- DNS FAILED: api.onfleet.com → [Errno -2] Name or service not known
- DNS OK: connect.roadie.com → 104.18.20.207
- DNS OK: api.burqup.com → resolves fine
The container's /etc/resolv.conf shows Railway's internal DNS (fd12::10). Writing Google DNS (8.8.8.8) to resolv.conf doesn't help — the resolution still fails for api.onfleet.com specifically.
This has been happening since the service was first deployed on April 2. I need outbound HTTPS access to api.onfleet.com for my delivery management integration.
Service URL: onfleet-roadie-production.up.railway.app
Region: us-east4-eqdc4a
Can you check if there's a network-level block on this domain?
1 Replies
2 months ago
Our public DNS lookup for api.onfleet.com also returns no records (A, AAAA, CNAME, TXT all empty), while the root domain onfleet.com resolves normally. This means api.onfleet.com is not resolvable from anywhere on the internet right now, not just from your Railway service. This is an issue on Onfleet's DNS side, not a network-level block on our end. You may want to check with Onfleet whether that hostname has changed or if there's a DNS misconfiguration on their end.
Status changed to Awaiting User Response Railway • about 2 months 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