5 days ago
Hi, I'm trying to add survey.palmering.com as a custom domain on the palmering service (project: palmering, environment: production), alongside the existing working domain app.palmering.com on the same service.
The domain has been stuck showing "Waiting for DNS update" for several hours. I've already verified and ruled out the two most common causes:
DNS is correctly configured — confirmed via external nslookup:
CNAME survey.palmering.com → keorfmvy.up.railway.app (the exact target Railway provided)
TXT railway-verify.survey.palmering.com → railway-verify=08e95b6d21e6ba11a67f81fa0b390aed503cc3cd3bd812b9183aeb3360301452 (matches what Railway asked for)
Cloudflare proxy isn't the issue — I temporarily switched the CNAME to "DNS only" (unproxied) to rule out proxy interference with verification, waited, and it made no difference. I've since switched it back to proxied to match app.palmering.com.
I also tried removing the domain and re-adding it to force a fresh verification cycle — same result.
Could you check on your end why verification for survey.palmering.com isn't completing? Happy to provide any additional info needed.
1 Replies
5 days ago
Two DNS records need updating. First, the CNAME for survey.palmering.com currently points to keorfmvy.up.railway.app, but the expected target is jgzn7nck.up.railway.app (this likely changed when you removed and re-added the domain). Second, the TXT verification record is not resolving at all from public DNS. Make sure it is a TXT record on the host _railway-verify.survey.palmering.com (note the leading underscore) with the exact value shown in your Railway dashboard. Update both in Cloudflare, and once they propagate, verification should complete. You can reply here once you've made the changes and we can re-check.
Status changed to Awaiting User Response Railway • 5 days ago