My custom domain www.tomorrowsquirrel.com TXT record _railway has been live in DNS for over 24 hours but verification is stuck on yellow. CNAME is green. Can you manually trigger verification? Thanks!
#Custom domain is stuck on yellow
pure silo
tender basinBOT
Linked Railway resource: a673d48b / 6a83fee7 / 5dd3e998
jade relic
If you use www, you'll also need to add @ as a record.
Some DNS services don't support CNAME flattening (using @ as a record), so in that case, you'll need to use Cloudflare's DNS service.
sonic lance
Verification is stuck for me too on the txt record
sonic lance
@pure silo did it resolve for you?
@pure silo I deleted and started again, worked instantly
pure silo
<@1099364402018406551> I deleted and started again, worked instantly
Thanks! Glad your issue was resolved. Mine hasn't resolved yet. I deleted and started again yesterday but it didn't resolve the issue. I'll try again.
cerulean echo
hello, any news on this ? same problem here
arctic coral
hello, any news on this ? same problem here
Can you open your own help thread and provide the domain?
pure silo
hello, any news on this ? same problem here
Just checked. Not yet I'm showing TXT as yellow - not connected. Sorry you're having the same issue. Domain is www.tomorrowsquirrel.com.
pure silo
@cerulean echo @sonic lance This fixed my issue: Here's my problem. _railway-verify.www.tomorrowsquirrel.com returns nothing (NXDOMAIN). Railway is looking for the TXT record there, not at _railway.
Go to your domain provider's DNS and add a second TXT record:
Type: TXT
Host: _railway-verify.www
Value: railway-verify="your id from railway"
Leave the existing _railway record in place — just add this new one alongside it. Hopefully this helps.@jade relic I think you were trying to point me in this direction, so thanks! It just took me a while to go down this paty.
jade relic
<@975753389940039730> <@608298932900200458> This fixed my issue: Here's my probl...
You can remove the _railway record, there’s no use for it.