Please re-issue the certificate for delivery.doradosurfaces.com (follow-up to support AI thread)
mackbluey
HOBBYOP

7 hours ago

Hi Railway team,

This is a follow-up to my earlier support chat, "Custom domain stuck on DNS update"

What happened: the domain was stuck on "Waiting for DNS update" for several days. The CNAME row was verified, but the TXT row (_railway-verify.delivery) never cleared. I confirmed the DNS was correct:

  • TXT at _railway-verify.delivery.doradosurfaces.com returns exactly railway-verify=d6734139b2f11114e8c3bb3fcddb60f397e94ed5ab3699127f9d4504f0098622 from our authoritative nameserver (ns29.domaincontrol.com) and from 8.8.8.8. It is the only TXT record at that name.
  • delivery.doradosurfaces.com resolves to cbr8am9v.up.railway.app, the target Railway shows.

The support assistant found that the ownership check had never re-run after the TXT record was published, and it started a fresh verification and certificate issuance. It also said that re-issuing the certificate needs a member of the Railway team, which it cannot do itself.

Current status: [the domain now shows as verified / still shows "Waiting for DNS update"], and [https://delivery.doradosurfaces.com still shows "Not secure" in the browser / the certificate looks fine].

Could someone on the team re-issue (or confirm the status of) the certificate for delivery.doradosurfaces.com? I have not changed any DNS records and can provide anything else you need.

Thank you,

Adam

Awaiting User Response

2 Replies

Status changed to Awaiting Railway Response Railway • about 7 hours ago


7 hours ago

Your CNAME and TXT verification records are both correct and visible publicly, but the domain was still showing as unverified with the certificate stuck issuing, because the ownership check never re-ran after the TXT record went live.

We've started a fresh verification and certificate issuance for the domain, which may take a few minutes to complete. No DNS changes are needed on your side.


Status changed to Awaiting User Response brody • about 7 hours ago


brody

Your CNAME and TXT verification records are both correct and visible publicly, but the domain was still showing as unverified with the certificate stuck issuing, because the ownership check never re-ran after the TXT record went live. We've started a fresh verification and certificate issuance for the domain, which may take a few minutes to complete. No DNS changes are needed on your side.

mackbluey
HOBBYOP

6 hours ago

Appreciate it!


Status changed to Awaiting Railway Response Railway • about 6 hours ago


Status changed to Awaiting User Response Railway • about 6 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...