a month ago
I tried connecting my domain to the host which is Network Solution but it keeps crashing.
Pinned Solution
a month ago
Hey, the issue is coming from how DNS works between Network Solutions and Railway. Railway doesn’t provide a fixed IP, so you can’t use an A record. It needs a CNAME record instead.
The easiest fix is to use a subdomain instead of the main domain.
For example, instead of connecting example.com, use something like:
- www.example.com or
Then in Network Solutions DNS, create a CNAME record like this:
- Host: www (or app)
- Points to: your-app.up.railway.app
After that, go to Railway and add the same subdomain (like www.example.com) in the custom domain section.
This works because subdomains support CNAME records, even if the main domain doesn’t.
So basically:
- Don’t connect the root domain (example.com)
- Use a subdomain (www or app)
- Point it to Railway using CNAME
That should fix the issue
6 Replies
Status changed to Open Railway • about 1 month ago
a month ago
can you provide more detailed information so that I can help?
a month ago
The Domain is on Network Solution, when I try to connect it with Railway it crashes, I read that on Network Solution DNS you can only A record, but Railway doesn't give dedicated IP. I don't know how to link both.
a month ago
Hey, the issue is coming from how DNS works between Network Solutions and Railway. Railway doesn’t provide a fixed IP, so you can’t use an A record. It needs a CNAME record instead.
The easiest fix is to use a subdomain instead of the main domain.
For example, instead of connecting example.com, use something like:
- www.example.com or
Then in Network Solutions DNS, create a CNAME record like this:
- Host: www (or app)
- Points to: your-app.up.railway.app
After that, go to Railway and add the same subdomain (like www.example.com) in the custom domain section.
This works because subdomains support CNAME records, even if the main domain doesn’t.
So basically:
- Don’t connect the root domain (example.com)
- Use a subdomain (www or app)
- Point it to Railway using CNAME
That should fix the issue
a month ago
Still not going can you check if I'm doing anything wrong. I attached some screenshoot of how I connected on Network solutions and what it is showing on Railway
Attachments
shubhankartrivedi
Hey, the issue is coming from how DNS works between Network Solutions and Railway. Railway doesn’t provide a fixed IP, so you can’t use an A record. It needs a CNAME record instead. The easiest fix is to use a subdomain instead of the main domain. For example, instead of connecting [example.com](http://example.com), use something like: \- [www.example.com](http://www.example.com) or \- [app.example.com](http://app.example.com) Then in Network Solutions DNS, create a CNAME record like this: \- Host: www (or app) \- Points to: [your-app.up.railway.app](http://your-app.up.railway.app) After that, go to Railway and add the same subdomain (like [www.example.com](http://www.example.com)) in the custom domain section. This works because subdomains support CNAME records, even if the main domain doesn’t. So basically: \- Don’t connect the root domain ([example.com](http://example.com)) \- Use a subdomain (www or app) \- Point it to Railway using CNAME That should fix the issue
a month ago
Still not going can you check if I'm doing anything wrong. I attached some screenshoot of how I connected on Network solutions and what it is showing on Railway
shubhankartrivedi
Hey, the issue is coming from how DNS works between Network Solutions and Railway. Railway doesn’t provide a fixed IP, so you can’t use an A record. It needs a CNAME record instead. The easiest fix is to use a subdomain instead of the main domain. For example, instead of connecting [example.com](http://example.com), use something like: \- [www.example.com](http://www.example.com) or \- [app.example.com](http://app.example.com) Then in Network Solutions DNS, create a CNAME record like this: \- Host: www (or app) \- Points to: [your-app.up.railway.app](http://your-app.up.railway.app) After that, go to Railway and add the same subdomain (like [www.example.com](http://www.example.com)) in the custom domain section. This works because subdomains support CNAME records, even if the main domain doesn’t. So basically: \- Don’t connect the root domain ([example.com](http://example.com)) \- Use a subdomain (www or app) \- Point it to Railway using CNAME That should fix the issue
a month ago
Here
Attachments
Status changed to Open 0x5b62656e5d • about 1 month ago
Status changed to Solved 0x5b62656e5d • about 1 month ago