The domain status confirms the inconsistency you described: for new.retailx.co.za the verification host is correctly set to _railway-verify.new, but for client.retailx.co.za it is set to just _railway-verify, treating it as an apex domain. Your workaround is correct. Create a CNAME record for client pointing to uj8r42op.up.railway.app, and a TXT record at _railway-verify.client with the verification token shown in the dashboard. Once both propagate, the certificate should issue and verify normally, as it did for new.retailx.co.za.

my issue is that I did the workaround, but the verification didn't come yet

Public DNS currently shows no CNAME record on client.retailx.co.za and no TXT record at either _railway-verify.client.retailx.co.za or _railway-verify.retailx.co.za, so verification has nothing to match against yet. Please double-check at your DNS provider that the CNAME for client points to uj8r42op.up.railway.app and the TXT record is created under the hostname _railway-verify.client (not just _railway-verify) with the token from the dashboard.

I did all you requested : still not working.

Both records are required for verification to complete. The TXT at _railway-verify.client is still not resolving in public DNS, so please verify at your DNS provider that it was saved successfully. You also need a CNAME record for client pointing to uj8r42op.up.railway.app. Once both records are live and propagated, verification should proceed normally.

it's still not resolving

I am afraid there might be an issue with this : starting from the cname and txt values generation

cane you check thouroughly?

nslookup -type=cname client.retailx.co.za

Server: 192.168.1.1

Address: 192.168.1.1#53

Non-authoritative answer:

*** Can't find client.retailx.co.za: No answer

Authoritative answers can be found from:

client.retailx.co.za

origin = ns1.host-h.net

mail addr = postmaster.client.retailx.co.za

serial = 20260731

refresh = 86400

retry = 1800

expire = 3600000

minimum = 86400

Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

Did you add the DNS records to client.retailx.co.za? I wasn’t able to find anything attached to it.

yeah, I did.

what's strange is that I tried to create test.retailx.co.za, and railway directly found that it's a subdomain and generated ready to use CNAME and TXT

unlike for client.retailx.co.za, where it's set to root CNAME name is set to @ directly

Can you share a screenshot of page where you configured your DNS records?

hello there

sorry for keeping you waiting. I couldn't reach out to the one who set it up.