The TXT value must be the verification token that Railway provided (typically something like railway-verify=<long-token>). Railway requires this TXT record to verify domain ownership before the custom domain will become active

The TXT value must be the verification token that Railway provided (typically something like railway-verify=<long-token>). Railway requires this TXT record to verify domain ownership before the custom domain will become active

"I added the _railway-verify.petcarelocal.net TXT record this morning. It has been in place all day. Please manually trigger the verification on your end as soon as possible."

Thanks for adding the TXT record. Domain verification can still take some time depending on DNS propagation and caching, but if the record is visible publicly and the Railway dashboard has not picked it up after several hours, we can take another look.

Please make sure the record is exactly on _railway-verify.petcarelocal.net and that the value matches the token shown in Railway, including any railway-verify= prefix if Railway displayed one. If it still shows as waiting after that, send a screenshot of the Railway custom-domain verification panel so we can compare the expected token with the DNS record.

Domain seems to work just fine.