custom domain stuck on Waiting for DNS
rockymountainracingassociation
HOBBYOP

a month ago

Project ID: 9dabcc92-25bb-4213-ab86-388350a07a31

Service: rms-live-timing

Issue: Custom domain timing.rockymountainspeedway.ca stuck on "Waiting for DNS update" — DNS fully propagated globally (CNAME + TXT both verified worldwide via dnschecker.org). Have deleted and re-added the domain multiple times over several days. Please manually trigger domain verification and SSL certificate issuance.

$10 Bounty

2 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


swastikiit2023
FREE

a month ago

Before assuming a Railway-side issue, verify:

  1. timing.rockymountainspeedway.ca resolves only to the Railway CNAME.
  2. No A/AAAA records exist for the same hostname.
  3. Cloudflare proxy is disabled (DNS Only).
  4. TXT ownership record still matches Railway's expected token.
  5. DNSSEC is not misconfigured.

Run:

dig timing.rockymountainspeedway.ca CNAME +short

dig timing.rockymountainspeedway.ca A +short

dig timing.rockymountainspeedway.ca AAAA +short

dig TXT _railway.timing.rockymountainspeedway.ca +short

If all results are correct and DNS has propagated globally, the domain verification queue or SSL issuance on Railway is likely stuck and requires manual re-verification by Railway staff.


I can access your domain just fine now. Your issue seems to be resolved.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...