#Custom domain

64 messages · Page 1 of 1 (latest)

manic urchin
#

I am trying to use my custom domain and when configuring the DNS records (type: CNAME, Name: @), Godaddy does not allow it. After searching for a solution I found that the problem is due to a fundamental DNS limitation: CNAME records cannot exist at the root domain level (using @) according to RFC standards. Any suggestion?

wraith houndBOT
#

Project ID: N/A

manic urchin
#

N/A

spiral flint
manic urchin
#

Am I allowed to do so even if the domain was purchased through godaddy?

#

@spiral flint

spiral flint
#

Yes, while I haven't used Godaddy myself, I have successfully guided other users with the same problem.

manic urchin
#

Good, thank you

#

It could be added as a warning

spiral flint
manic urchin
#

yes

spiral flint
# manic urchin yes

I see, would you mind opening a #1157406325593096264 thread regarding this?

manic urchin
#

Done, thank you

manic urchin
#

@spiral flint This is the error I am receving when adding a CNAME @ record

#

Any suggestion?

#

Current records

spiral flint
#

Please delete the A records in this case

manic urchin
#

Please explain why

spiral flint
#

Because they are conflicting as per the error you just mentioned

manic urchin
#

Deleting both of them?

spiral flint
#

Yes

manic urchin
#

They were copied from godaddy I guess. What do you think they were pointing to?

#

Trying to get my head around it

#

CNAME was added successfully

#

Hence only these two records are enough?

spiral flint
spiral flint
manic urchin
#

Thank you. I guess I have to wait for them to propagate

spiral flint
manic urchin
#

Should be good

spiral flint
#

No, it has to be Full and not Full (strict)

manic urchin
#

Modified, thank you

spiral flint
#

Can you confirm that your application is now reachable?

manic urchin
#

It is not

#

Should I add it again in the UI and allow it to detect cloudflare?

spiral flint
#

You can try it if you want to, but it looks like that everything is configured correctly, as I can access it via Google's DNS servers.

manic urchin
#

Ok thank you I receive the error 400 as well

spiral flint
manic urchin
#

Yes

#

Just added the domain again and still getting same message on the railway ui

spiral flint
#

Did you also add the CNAME record again?

manic urchin
#

Yes

#

The new one

spiral flint
manic urchin
#

I can reach the website now but I still get the same message in the ui

manic urchin
manic urchin
spiral flint
#

You didn't add the www subdomain or create a redirect rule in Cloudflare.

manic urchin
spiral flint
#

No, you will have to add it too

manic urchin
#

ok thank you. Last question, should the railway ui message update itself or is it a bug?

spiral flint
#

It will be updated, however this may take some time

manic urchin
#

Appreciate your help, Any way I can leave a positive review for the support you gave?

spiral flint
#

I am not aware of a way to leave a review via Discord, you may try https://station.railway.com/questions/custom-domain-6e3f2fac if you really wish to.

Railway Help Station

I am trying to use my custom domain and when configuring the DNS records (type: CNAME, Name: @), Godaddy does not allow it. After searching for a solution I found that the problem is due to a fundamental DNS limitation: CNAME records cannot exist at the root domain level (using @) according to RFC standards. Any suggestion?

#

In any case, I'll mark this thread as solved for now. 🙂

#

!s