11 days ago
The TXT record will not update on a project i am an author on need to update the record on railway so we can publish. thanks
7 Replies
11 days ago
We don't see any custom domains on the account you're writing from, so the domain's records can't be viewed or changed from here. The TXT verification record isn't updated on our side: it has to be added at the DNS provider that manages the domain, using the exact host and value shown on that domain's entry in the service's Settings, under Networking, in the project where the domain was added.
Status changed to Awaiting User Response Railway • 11 days ago
Railway
We don't see any custom domains on the account you're writing from, so the domain's records can't be viewed or changed from here. The TXT verification record isn't updated on our side: it has to be added at the DNS provider that manages the domain, using the exact host and value shown on that domain's entry in the service's Settings, under Networking, in the project where the domain was added.
11 days ago
yes its on a project which is not under my account directly. but i have access to. 8jvx2921.up.railway.app
Status changed to Awaiting Railway Response Railway • 11 days ago
11 days ago
The address you shared is not a service domain on any project. It matches the format of the CNAME target we generate for a custom domain, so it is the value your domain's CNAME record points to, not something that holds a TXT record.
The TXT verification record can't be updated from our side, even for project members. It has to be created at the DNS provider that manages the custom domain, using the exact TXT host and value shown on that domain's entry in the service's Settings, under Networking, in the shared project. If you don't manage that domain's DNS yourself, whoever controls the domain's DNS provider needs to add it.
Status changed to Awaiting User Response Railway • 11 days ago
Railway
The address you shared is not a service domain on any project. It matches the format of the CNAME target we generate for a custom domain, so it is the value your domain's CNAME record points to, not something that holds a TXT record. The TXT verification record can't be updated from our side, even for project members. It has to be created at the DNS provider that manages the custom domain, using the exact TXT host and value shown on that domain's entry in the service's Settings, under Networking, in the shared project. If you don't manage that domain's DNS yourself, whoever controls the domain's DNS provider needs to add it.
11 days ago
yes its already added just needs to be updated.
Status changed to Awaiting Railway Response Railway • 11 days ago
11 days ago
Updating an existing TXT record works the same way as adding one. The record lives at the DNS provider that manages the custom domain, not on our side, so it has to be edited there. Being a member of the project doesn't change this.
Whoever controls that domain's DNS needs to change the existing _railway-verify TXT value so it matches exactly what the shared project currently shows for that domain under the service's Settings, in Networking. If that value differs from the one published earlier, the domain entry was removed and re-added on the project. Each new entry gets a new verification token and CNAME target, so the CNAME may need updating too.
Verification picks up on its own once the updated records have propagated, so there's no need to remove and re-add the domain again.
Status changed to Awaiting User Response Railway • 11 days ago
11 days ago
on railway side it needs to be updated, as it is saying DNS propgated. everything is on the DNS side, yet waiting on RAILWAY. to re check that the TXT record is correct. so then the Cert can be created.
Status changed to Awaiting Railway Response Railway • 11 days ago
11 days ago
No manual re-check is needed. Ownership verification keeps retrying on its own, and the certificate is issued automatically as soon as the _railway-verify TXT record resolves to the exact token shown for that domain in the shared project's service Settings, under Networking. A manual re-issue would stop at the same check.
If the dashboard still shows the domain waiting, the TXT value being served publicly does not yet match the token on the current domain entry, or the CNAME does not point at the target shown there. If the domain was ever removed and re-added, both values changed, so compare them character for character with what the dashboard shows now.
The domain is not on the account you're writing from, so we can't read its status from here. Please share the custom domain hostname itself (not the CNAME target) so we can check what our side currently sees for it.
Status changed to Awaiting User Response Railway • 11 days ago
Status changed to Solved strion • 11 days ago