24 days ago
Hello Railway App community or Railway support,
I'm experiencing issues with my custom domain that has been ongoing for a couple of days.
Problem:
My Railway service is running perfectly on the default Railway URL
Custom domain is a subdomain for backend works intermittently - sometimes loads, sometimes shows "ERR_CONNECTION_CLOSED"
CNAME verification shows yellow warning in Railway dashboard despite DNS being correctly configured
DNS Configuration (Verified via dig command):
CNAME
TXT
Both records are correctly configured in Route 53 and propagated globally (confirmed via dig commands).
What I've Tried:
Verified DNS records multiple times with dig - all correct
Waited over more than 30 hours for verification
Removed and re-added domain multiple times
Updated CNAME values as Railway changed them
Tested Railway default URL - works perfectly every time
Request: I need this domain to work reliably for production. Any suggestion or support that can help me sort this out. I am not sure if Railway Support will help me verify the domain manually.
Thank you for your help!
Kind regards
Biplob
4 Replies
24 days ago
Can you share a ss containing the domain you are trying to add in railway & a ss containing the provided records being added in your DNS provider?
24 days ago
Hi thanks for looking into my issue. The domain is https://myapi.mypensionflow.com and I have attached screenshots.
Attachments
23 days ago
Hey, quick question
Are you trying to add allwildcards for your domain - *.mypensionflow.com or just myapi.mypensionflow.com.
Your website seems to be working for mypensionflow.com
23 days ago
1 of the 5 name servers on your domain is responding with IPs, instead of a CNAME like the rest:
$ dig myapi.mypensionflow.com @NS2.VERCEL-DNS.COM
; <<>> DiG 9.20.18 <<>> myapi.mypensionflow.com @NS2.VERCEL-DNS.COM
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53218
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;myapi.mypensionflow.com. IN A
;; ANSWER SECTION:
myapi.mypensionflow.com. 1800 IN A 64.29.17.1
myapi.mypensionflow.com. 1800 IN A 216.198.79.1
$ dig myapi.mypensionflow.com @NS-1524.AWSDNS-62.ORG
; <<>> DiG 9.20.18 <<>> myapi.mypensionflow.com @NS-1524.AWSDNS-62.ORG
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63262
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;myapi.mypensionflow.com. IN A
;; ANSWER SECTION:
myapi.mypensionflow.com. 300 IN CNAME n36unujg.up.railway.app.
;; AUTHORITY SECTION:
mypensionflow.com. 172800 IN NS ns-1524.awsdns-62.org.
mypensionflow.com. 172800 IN NS ns-1702.awsdns-20.co.uk.
mypensionflow.com. 172800 IN NS ns-358.awsdns-44.com.
mypensionflow.com. 172800 IN NS ns-883.awsdns-46.net.
I suggest you remove that name server from your domain.