Custom domain bio.cope.com stuck on "Waiting for DNS update" despite correct DNS
michellehavnt
PROOP

22 days ago

Hi team,

Custom domain bio.cope.com on our bio-link service (project: faithful-vitality) has been stuck on "Waiting for DNS update" since we added it this morning. The CNAME row shows green ✓ but the TXT row stays yellow ⚠.

Both DNS records are correctly published and globally propagated. Confirmed from public resolvers and authoritative nameservers:

$ dig bio.cope.com CNAME +short

shdakbsf.up.railway.app.

$ dig _railway-verify.bio.cope.com TXT +short

"railway-verify=f136e95ec51bf8f6d60c76a6b7cc3f21c3ef61c5c5c1b9192c8184d5bb8c877e"

$ dig @dns1.registrar-servers.com _railway-verify.bio.cope.com TXT +short

"railway-verify=f136e95ec51bf8f6d60c76a6b7cc3f21c3ef61c5c5c1b9192c8184d5bb8c877e"

Requests to https://bio.cope.com return HTTP 404 with x-railway-fallback: true and the default *.up.railway.app cert, confirming the domain hasn't been mapped to our service at the edge yet.

DNS is managed by our dev team, so I'd prefer not to rotate the TXT token via remove + re-add. The current token matches what's live in DNS - could you please trigger a re-verification from your side?

Thank you so much for your help.

Best,

Michelle

bio-link 2026-05-26 at 7.32.22 pm.png

Attachments

Solved$20 Bounty

Pinned Solution

Have you tried removing the domain from Railway and add it back after ~10-15 mins? (Make sure to update DNS records as necessary).

3 Replies

Railway
BOT

22 days 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 22 days ago


It may take up to a few hours (maybe even a day, but rarely) for Railway to validate the DNS and issue a certificate. If that doesn’t happen by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.


0x5b62656e5d

It may take up to a few hours (maybe even a day, but rarely) for Railway to validate the DNS and issue a certificate. If that doesn’t happen by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.

michellehavnt
PROOP

21 days ago

Its more then 24 hours ago that the DNS were added, still no change. Could you please trigger a re-verification from your side?


Have you tried removing the domain from Railway and add it back after ~10-15 mins? (Make sure to update DNS records as necessary).


Status changed to Solved sam-a 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...