3 hours ago
Hi,
I'm trying to verify domain ownership with my hosting provider (Railway) via a TXT record, but it's not publishing.
Record saved in Dynadot panel:
- Type: TXT
- Subdomain:
_railway-verify.www - Value:
railway-verify=df6eb467804527c24040e5ef92befb464d7100742b63934fcb06d2b16d30cdc5
Problem: 30+ minutes after saving, the record does not appear on your nameservers or any public DNS resolver (checked Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9). The CNAME for the same domain published fine earlier today.
Can you check why this TXT record isn't being published to the DNS zone?
1 Replies
3 hours ago
Your _railway-verify.www TXT record is publishing now, and it resolves publicly with the value you saved. The domain currently attached to your service is the root domain rather than the www subdomain, though, so it is checking a different record that does not exist yet.
At Dynadot, add a TXT record with the subdomain _railway-verify (no www) and the value railway-verify=ad99baf1a882431bd820f234a3b94eeafe15a1abdcd666ef56b5a0fe37c7b265. The record you published for www uses a token from an earlier version of the domain and will not verify the current one.
Your CNAME also points to an older Railway target than the one the domain now expects. Update it to the target shown for that domain in your service's networking settings. Verification and the certificate continue on their own once both records resolve.
Status changed to Awaiting User Response Railway • about 3 hours ago