Skip to content
Custom subdomain still waiting for DNS verification after 24 hours; Railway wildcard certificate served
Anonymous
OP

a month ago

I'm setting up admin.gukateam.com on an existing Railway service. The service is Online and its latest deployment succeeded, but the custom domain still says "Waiting for DNS update" on target port 8080.

Both DNS records requested by Railway were saved on 16 October 2026 at 14:42 Asia/Jerusalem (11:42 UTC):

  • CNAME admin points to dfa59uj6.up.railway.app.
  • The TXT at _railway-verify.admin contains the exact verification value shown in Railway's Configure DNS Records dialog. I have omitted that token from this public post.

The CNAME and TXT were publicly resolvable by 14:43 local time, and still resolve correctly more than 24 hours later (last checked 17 October at 14:57 local). The Railway dialog still requires the same records and the domain status has not changed. DNS is hosted at Namecheap, not behind a Cloudflare proxy. Public DNS checks found no CAA record at the parent domain and no DS delegation for it.

As of 17 October at 14:57 local time, HTTPS requests to both https://admin.gukateam.com/health and https://admin.gukateam.com/login still fail normal hostname verification. The TLS certificate presented for this hostname covers *.up.railway.app and up.railway.app, not admin.gukateam.com. I have not bypassed certificate validation or attempted sign-in through the invalid certificate.

I read your SSL troubleshooting guide and understand issuance can sometimes take up to 72 hours. I have not deleted/re-added the domain or repeatedly triggered certificate requests.

Could you check whether domain ownership verification or certificate provisioning is stuck, or advise a safe way to inspect/retrigger verification without deleting the domain? I can provide the project/service/deployment identifiers and exact verification record through an appropriate private support route if needed.

This blocks first-time access to the new admin service; it is not a production application outage. No application-code debugging is requested.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

Both of your records are correct: the CNAME resolves to the target we expect and the TXT value matches your verification token exactly, but ownership verification never re-ran after they went live, so the certificate stayed stuck.

We've started a fresh verification and certificate issuance for that domain, which can take a few minutes to complete. There's no need to delete or re-add the domain or change any DNS records.


Status changed to Awaiting User Response brody • about 1 month ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...