Hi — my custom domain is stuck on "Waiting for DNS" (yellow triangle) and

won't verify or issue a certificate, even though DNS is fully correct and

propagated. Could you force a re-verification / cert issuance?

Domain: www.quinsqualitycleaning.com

CNAME target Railway assigned: x1wxp4u1.up.railway.app

DNS is confirmed correct from every resolver, including GoDaddy's own

authoritative nameserver:

• GoDaddy authoritative (ns41.domaincontrol.com): www -> x1wxp4u1.up.railway.app
• Google (8.8.8.8): www -> x1wxp4u1.up.railway.app
• Cloudflare (1.1.1.1): www -> x1wxp4u1.up.railway.app

Symptoms:

• Railway still shows "Waiting for DNS" for over an hour.

• Hitting the domain returns HTTP 404 (host not attached), and TLS still

  serves the default .up.railway.app certificate (CN=.up.railway.app) —

  the Let's Encrypt cert for my domain has never been issued.

It's a single clean CNAME (no conflicting records, no restrictive CAA). The

service works perfectly on its temporary *.up.railway.app URL, so the app

itself is healthy — only the custom domain won't verify.

Things I've already tried:

• Waited well over an hour with DNS stable.

• Redeployed the service.

• Removed and re-added the domain (this only generated a new target each

  time and restarted the wait).

Can you please force the domain check / certificate issuance on your end, or

tell me what's blocking verification? Thank you! Got it — so for my domain I need to add a TXT record under

_railway-verify. Can you give me the exact TXT record for MY domain

(www.quinsqualitycleaning.com)? Specifically:

1. The exact record NAME/HOST (the _railway-verify... for my domain)
2. The exact VALUE/token I should put in it

I'll add it at GoDaddy right away.