DNS resolution failure for api.ebay.com inside Railway runtime
vermaisrahul
PROOP

a month ago

Hi Railway Team,

DNS resolution for api.ebay.com is failing inside Railway runtime.

This is not an application code issue. I created a fresh Railway service and used only this start command:

python -c "import socket; print(socket.gethostbyname('api.ebay.com'))"

It fails with:

socket.gaierror: [Errno -5] No address associated with hostname

I also tested:

python -c "import socket; print(socket.getaddrinfo('api.ebay.com', 443))"

It fails with:

socket.gaierror: [Errno -2] Name or service not known

But this works:

python -c "import socket; print(socket.getaddrinfo('www.ebay.com', 443))"

It returns IP addresses successfully.

So the issue is specific to resolving api.ebay.com / global-api.ebaycdn.net from Railway runtime.

My production FastAPI service is failing eBay OAuth token calls to:

https://api.ebay.com/identity/v1/oauth2/token

Error from production logs:

httpx.ConnectError: [Errno -2] Name or service not known

/etc/resolv.conf inside Railway container shows:

search internal railway.internal

nameserver fd12::10

Please check DNS resolution for api.ebay.com from my Railway runtime/region.

Project ID:

Service name: Listaris

Environment: production

Railway region: US WEST

Deployment ID: d608be18-09da-4d1c-9f99-a345f5241ce6

Approx start time: 2026-04-26 23:00 UTC onward

$20 Bounty

1 Replies

Railway
BOT

a month ago

Our DNS lookup confirms that api.ebay.com has a CNAME pointing to global-api.ebaycdn.net, but that target currently returns no A or AAAA address records from the public internet either, meaning this is not specific to our DNS resolver. The CNAME chain terminates at a hostname with no address records, which is an eBay-side CDN/DNS configuration issue (likely geo-dependent responses from their CDN that don't serve records for certain resolver locations). We'd recommend reporting this to eBay's developer support, as the resolution failure originates from their DNS infrastructure, not ours.


Status changed to Awaiting User Response Railway 26 days ago


Status changed to Awaiting Railway Response Railway 26 days ago


Railway
BOT

a month 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 Railway 26 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...