a month ago
My service (ai-hairstyles-production.up.railway.app) shows as Online in the dashboard, but the hostname resolves to 69.46.46.63 on both Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1). This isn't the private networking issue from yesterday — it's the public authoritative DNS for up.railway.app returning a bad IP. My custom domain (aihairstyles.com) CNAMEs to this hostname so it's also down. Started around [time] today.
20 Replies
a month ago
ai-hairstyles-production.up.railway.app loads fine for me, what are you seeing exactly?
the actual domain I have set for it, aihairstyles.com is suddenly giving an https cert issue error
Attachments
a month ago
Could you go to your service's settings > public networking, press on "DNS records" for the custom domain, screenshot the popup & send it here
And then go to your DNS provider and tell me what the _railway-verify value is set to?
Sorry for the screenshot spam. I have a few set up it seems. did this years ago
a month ago
Might be worth removing and re-adding the apex custom domain, temporary fix perhaps
yeah Claude is telling me that the @ cname is mismatched with my namecheap records now that I've given it those screenhots. Checking
a month ago
Could you try changing the apex's record type to ALIAS from CNAME?
CNAME at apex isn't possible, Namecheap has the ALIAS record type to fix this
a month ago
Tried this yet?
added it, the DNS warning went away (I guess because railway verified that the records had been propogated?) Still https cert issue
Attachments
a month ago
I personally don't know what further steps to take, apologies
There does seem to be an existing station thread similar to this
a month ago
Switching to Cloudflare for DNS might help
a month ago
(Cloudflare is generally recommended for DNS anyways!)