Title: Production domain not resolving - DNS_PROBE_FINISHED_NXDOMAIN error
parag7823
HOBBYOP

10 months ago

Myy deployment is successful but the domain is not resolving. Error: DNS_PROBE_FINISHED_NXDOMAIN Domain:friendly-greetings-launchpad-production-2a5b.up.railway.app

Status: - Deployment: Active - Healthcheck: Passing (GET /health returns 200 OK) - Logs: "INFO: Uvicorn running on http://0.0.0.0:8080" - Backend: FastAPI + React (Vite) - Region: EU West (Amsterdam)

What I've Tried: - Generated new domain multiple times - Verified $PORT configuration is correct - Waited 30+ minutes for DNS propagation - Tested different browsers and cleared DNS cache - Checked logs - no errors found GitHub:https://github.com/Parag7823/friendly-greetings-launchpad

The app deploys successfully and healthcheck passes, but the domain doesn't resolve. Please help investigate this DNS/networking issue. Thank you!

$10 Bounty

4 Replies

Railway
BOT

10 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


10 months ago

Hey,

This looks like it was just a caching issue. Caching can happen on the network level, above the browser.

Can you confirm that this is working now?


naimmalek
HOBBY

10 months ago

similar issue getting.

public domain of railway xx-production.up.railway.app working fine

but attached custom domain giving me returns DNS_PROBE_FINISHED_NXDOMAIN error often a day. after 2-3 mins it's automatically got resolved but why i am getting this error. this should be fixed


naimmalek

similar issue getting. public domain of railway [xx-production.up.railway.app](http://xx-production.up.railway.app) working fine but attached custom domain giving me returns DNS\_PROBE\_FINISHED\_NXDOMAIN error often a day. after 2-3 mins it's automatically got resolved but why i am getting this error. this should be fixed

10 months ago

Are you also using Cloudflare?

EDIT: Please make a new thread for this issue.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...