Domain DNS Not Resolving Globally After CDN Incident (March 30)
aifintemp01
FREEOP

2 months ago

My service domain is not resolving globally across multiple devices and networks, despite the service being online and operational.

Service Details:

  • Project: stunning-presence
  • Service: aifin
  • Domain: aifin-production.up.railway.app
  • Port: 8000
  • Current Deployment ID: 378e23b7-becb-46d5-b8d7-bea5c985cd5c
  • Deployment Status: SUCCESS

Issue: All devices (laptop, phone, tablet) across different networks show:

DNS_PROBE_FINISHED_NXDOMAIN
This site can't be reached
Check if there is a typo in aifin-production.up.railway.app.

Workaround Confirms Backend is Fine:

  • Domain resolves and works perfectly when using Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1)
  • Application logs show successful startup and requests being processed
  • No errors in deployment or application logs

Timeline:

  • Deployment created: 2026-03-30 16:41:11 UTC
  • Issue persists after Railway CDN incident resolution (11:30 UTC)
  • Tested across multiple devices/networks - all fail with ISP DNS, all work with Google DNS

Root Cause Analysis: This appears to be related to the CDN incident reported on March 30 at 12:20 UTC. The domain DNS is not propagating globally through standard ISP DNS servers, suggesting the domain routing was not fully restored after the incident resolution.

Request: Please investigate why aifin-production.up.railway.app is not resolving through standard DNS servers globally, and restore proper DNS propagation.

Solved

1 Replies

Railway
BOT

2 months ago

Your domain aifin-production.up.railway.app is active and resolving correctly from our side, returning an A record of 151.101.2.15. Since it works on Google DNS and Cloudflare DNS but not on your ISP's DNS servers, this indicates your ISP's resolvers cached a negative (NXDOMAIN) response, likely during the CDN incident window on March 30, and have not yet refreshed that cached entry. The TTL on negative DNS cache entries varies by ISP and can persist for hours to days. Flushing your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS) and restarting your router may help, but the ISP-side cache will clear on its own once the negative TTL expires.


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

2 months 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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...