a year ago
Hi, we've added the CNAME records for Railway in our DNS provider, Namecheap according to the instructions for custom domains here: https://docs.railway.app/guides/public-networking
This works fine until we tried verifying our site with Google Site Verification which requires TXT records to be added to our DNS Host records. For some reason, they conflict with the Railway CNAME records and we keep failing Google Site Verification.
Does anyone know how we can fix this issue - we need both to work!
6 Replies
a year ago
Hello,
I don't think there is a TXT record on the domain to begin with?
https://www.nslookup.io/domains/tupai.ai/dns-records/
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
That's the crux of the matter. In the screenshot below, the Google site verification code has been added, but doing a lookup does not reveal the TXT records. However, after removing the CNAME for Railway, the TXT records are viewable via the DNS lookup. How do we fix this? Are we missing some configuration, specifically for Namecheap, our DNS provider?
Attachments
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
Gotcha, you would need to use Cloudflare's nameservers with the orange cloud turned on, this will allow you to have a CNAME and TXT at the root.
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Just to clarify, I should set-up Cloudflare nameservers as my DNS in Namecheap, then turn the orange cloud on at the Cloudflare configuration? Currently, we haven't set up Cloudflare.
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Awaiting User Response Railway • over 1 year ago
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Solved david • over 1 year ago