Project: vdvpro-website-v2 (production service) Custom domains: vdvpro.nl and www.vdvpro.nl Both domains remain on "Waiting for DNS update" with the TXT verification records showing a warning, even though all required DNS records have been correctly configured for several hours and are globally propagated (verified via Google DNS 8.8.8.8 and Cloudflare 1.1.1.1): - vdvpro.nl A -> 69.46.46.15 - www.vdvpro.nl CNAME -> i7fbfs7k.up.railway.app - _railway.vdvpro.nl TXT -> railway-verify=ab1f7a27e45f455f49fc66788c26c2c449f500cda0e351ef536e5cf1babe41a1 - _railway.www.vdvpro.nl TXT -> railway-verify=1db18152842d47baeaf36614d4e99b0fa884ba7feb2a385ac5287ac44bad01c9 The CNAME checks already show green, but the TXT verification stays pending and no domain-specific Let's Encrypt certificate is issued (the endpoint still serves the generic *.up.railway.app certificate, so HTTPS fails on the custom domain). I have already: - Removed and re-added both custom domains - Updated the CNAME/TXT records to match the new values Railway generated - Triggered a redeploy None of this resolved the issue. Note: there is an ongoing "Degraded Storage Performance" incident shown in my dashboard, which may be related. Could you please re-trigger domain verification and certificate issuance for these two domains? Thank you.

Subject: Custom domain stuck on "Waiting for DNS update" — no SSL certificate issued despite correct DNS

richardvandev

PROOP

a month ago

Project: vdvpro-website-v2 (production service)

Custom domains: vdvpro.nl and www.vdvpro.nl

Both domains remain on "Waiting for DNS update" with the TXT verification

records showing a warning, even though all required DNS records have been

correctly configured for several hours and are globally propagated

(verified via Google DNS 8.8.8.8 and Cloudflare 1.1.1.1):

vdvpro.nl A -> 69.46.46.15
www.vdvpro.nl CNAME -> i7fbfs7k.up.railway.app
_railway.vdvpro.nl TXT -> railway-verify=ab1f7a27e45f455f49fc66788c26c2c449f500cda0e351ef536e5cf1babe41a1
_railway.www.vdvpro.nl TXT -> railway-verify=1db18152842d47baeaf36614d4e99b0fa884ba7feb2a385ac5287ac44bad01c9

The CNAME checks already show green, but the TXT verification stays pending

and no domain-specific Let's Encrypt certificate is issued (the endpoint

still serves the generic *.up.railway.app certificate, so HTTPS fails on the

custom domain).

I have already:

Removed and re-added both custom domains
Updated the CNAME/TXT records to match the new values Railway generated
Triggered a redeploy

None of this resolved the issue. Note: there is an ongoing "Degraded Storage

Performance" incident shown in my dashboard, which may be related.

Could you please re-trigger domain verification and certificate issuance for

these two domains? Thank you.

Solved$20 Bounty

2 Replies

Railway

BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway • 28 days ago

0x5b62656e5d

MODERATOR

a month ago

The TXT records need to be on _railway-verify, not _railway.

0x5b62656e5d

MODERATOR

a month ago

Also, Railway does not support using A records. If your DNS provider doesn't support CNAME flattening (using CNAME records on root domains), I'd suggest migrating to Cloudflare's DNS service.

Status changed to Solved richardvandev • 28 days ago

Welcome!