Hello, I am trying to link my custom domains to my service, but the status is stuck on "Waiting for DNS update" and the SSL certificates are not generating. I have updated the DNS records on my registrar (Gandi) more than 15 hours ago, and they are fully propagated and resolving correctly globally, but Railway's verification system doesn't seem to detect them. Here are the details: 1. Subdomain: www.ephysia.com - Target CNAME: i46fzcec.up.railway.app (currently resolves to 66.33.22.35) - TXT Record (_railway-verify.www): "railway-verify=06181ad4989d77b522b151f7ff409a47ef0e8544" (fully resolving) 2. Root domain: ephysia.com - Target ALIAS: blkqc018.up.railway.app (currently resolves to 66.33.22.42) - TXT Record (_railway-verify): "railway-verify=5959041db6a96c56c7e9c1667596d4bf62e3d360" (fully resolving) Could you please clear the DNS verification cache for my service / project and manually trigger the verification check and Let's Encrypt SSL certificate generation? Thank you!

DNS verification stuck for custom domains ephysia.com and www.ephysia.com

mediances-ops

PROOP

16 days ago

Hello,

I am trying to link my custom domains to my service, but the status is stuck on "Waiting for DNS update" and the SSL certificates are not generating.

I have updated the DNS records on my registrar (Gandi) more than 15 hours ago, and they are fully propagated and resolving correctly globally, but Railway's verification system doesn't seem to detect them.

Here are the details:

Subdomain: www.ephysia.com

Target CNAME: i46fzcec.up.railway.app (currently resolves to 66.33.22.35)
TXT Record (_railway-verify.www): "railway-verify=06181ad4989d77b522b151f7ff409a47ef0e8544" (fully resolving)

Root domain: ephysia.com

Target ALIAS: blkqc018.up.railway.app (currently resolves to 66.33.22.42)
TXT Record (_railway-verify): "railway-verify=5959041db6a96c56c7e9c1667596d4bf62e3d360" (fully resolving)

Could you please clear the DNS verification cache for my service / project and manually trigger the verification check and Let's Encrypt SSL certificate generation?

Thank you!

$20 Bounty

2 Replies

Railway

BOT

16 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 • 16 days ago

0x5b62656e5d

MODERATOR

16 days ago

Your TXT record seems malformed. Make sure you're clicking the button to copy the entire content for the TXT record instead of manually selecting it.

avnish-es

HOBBYTop 10% Contributor

16 days ago

investigated the issue from multiple public resolvers and the DNS records appear to be correctly propagated.

Verification performed:

Google DNS (8.8.8.8) resolves both Railway verification TXT records.

Cloudflare DNS (1.1.1.1) resolves both Railway verification TXT records.

Authoritative Gandi nameservers return the same verification values.

www.ephysia.com resolves to the expected Railway CNAME target.

ephysia.com resolves to the expected Railway IP.

Additionally:

HTTPS is working for both ephysia.com and www.ephysia.com.

Let's Encrypt certificates have already been issued and are being served successfully.

TLS handshakes complete successfully and the certificates validate correctly.

Based on these results, it appears DNS verification and certificate issuance have succeeded on the platform side.

If the Railway dashboard is still showing "Waiting for DNS update", the issue may be a stale verification state or delayed status synchronization rather than a DNS propagation problem.

Could someone verify whether the custom-domain verification status is stuck in the dashboard despite successful verification and certificate provisioning?

Welcome!