Hi Railway team,

My custom domain has been stuck on "Waiting for DNS update" for several

days and never completes verification, even though DNS is fully

propagated on my side.

Domain: demo.dontworry.ai.kr

DNS records (verified via Google DNS and Cloudflare DNS):

CNAME demo.dontworry.ai.kr

     → tnsou5kv.up.railway.app

TXT _railway-verify.demo.dontworry.ai.kr

     → railway-verify=29984a45bccd39f9a4a5e468534912016d22c28ce158c2246cf3cd67a3e3936a

Both resolve correctly and match the exact values shown in the Railway

dashboard under Settings → Networking → Show DNS records.

What I've already tried:

• Removed and re-added the custom domain three times, updating both

  CNAME and TXT at the registrar each time. Still stuck.

• Confirmed both records in Gabia match the dashboard exactly,

  character by character.

• Confirmed the domain is not registered on any other Railway project.

• Checked status.railway.com — Fully Operational.

Current behavior:

HTTP → 301 redirect (requests do reach Railway)

HTTPS → fails; the served certificate is *.up.railway.app,

      not one issued for my domain

Setup details:

• Registrar: Gabia (.ai.kr domain)

• Authoritative nameservers resolve to Cloudflare

  (elliott.ns.cloudflare.com), which appears to be the registrar's own

  DNS infrastructure. I do not have a Cloudflare account, so no proxy

  (orange cloud) is involved.

• TTL: 600

Since DNS resolves correctly from public resolvers and HTTP requests

already reach Railway, it looks like the verification isn't completing

on Railway's end. Could you force a manual re-verification for this

domain?

Thanks!