a month ago
I've connected a custom domain (swbfiirankings.com) to my Railway service, but DNS is not resolving correctly after changing nameservers.
What I did:
Changed domain nameservers from GoDaddy to Cloudflare (kiki.ns.cloudflare.com, vicky.ns.cloudflare.com)
Created CNAME record in Cloudflare: swbfiirankings.com → web-production-11e48.up.railway.app
Connected the domain to my Railway web service
The problem: It's been almost 1 hour since the nameserver change, but DNS is still resolving to the old GoDaddy IP instead of Railway.
DNS test results:
nslookup -q=NS swbfiirankings.com 1.1.1.1
→ Still returns icp100.net nameservers (old cache)
nslookup swbfiirankings.com 8.8.8.8
→ Address: 69.46.46.40 (old GoDaddy IP, not Railway)
ICANN Registry Lookup shows:
Nameservers: KIKI.NS.CLOUDFLARE.COM, VICKY.NS.CLOUDFLARE.COM ✓ (correct)
Updated: 2026-07-15 15:21:37 UTC ✓ (change went through)
Domain Status: clientDeleteProhibited, clientRenewProhibited, clientTransferProhibited, clientUpdateProhibited
Cloudflare DNS Records are correctly configured:
swbfiirankings.com CNAME → web-production-11e48.up.railway.app (DNS only)
The nameservers are set correctly at the registry level, but DNS resolution isn't propagating globally. What's the next step?
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
This currently looks like normal nameserver-delegation caching rather than a Railway issue.
The key observation is that the .com registry already reports:
kiki.ns.cloudflare.com
vicky.ns.cloudflare.comwhile recursive resolvers such as 1.1.1.1 and 8.8.8.8 still return the previous icp100.net delegation and its old A record.
I would simply wait a little more before treating it as a propagation failure.
The listed clientDeleteProhibited, clientTransferProhibited, and similar domain statuses are registrar locks and do not by themselves prevent DNS resolution. A clientHold or serverHold status would be relevant, but neither was shown.
I would not delete and recreate the Railway custom domain or repeatedly change its CNAME while the nameserver delegation is still converging.
If dig +trace still shows the old nameservers after 24 hours, contact the registrar because the parent-zone delegation has not been published correctly. If the trace shows Cloudflare but only a particular recursive resolver remains stale, it is still a resolver-cache issue and should clear when that resolver's TTL expires.
a month ago
Check the DNS records in Cloudflare to make sure the proxy status is set to "DNS only" and not "Proxied
Railway might take up to 24 hours for domains verification
You can learn more at https://docs.railway.com/networking/domains/working-with-domains
Status changed to Open medim • about 1 month ago
Status changed to Solved medim • about 1 month ago