It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.

Make sure the txt records don't have any typo mistake or any quotation marks and it is routed to the relevant sub domain.

Railway sometimes can take 24-48 hours for txt verification.

Also validate your verificationToken under status.

If issue persists, try removing the domain from your service and re add the domain to your service after 15-30 mins of removal. Then re configure your DNS records. It would refresh any pending connections.

I deleted the record yesterday and added again an hour ago but Still TXT is not verified. I have copied the values from railway so i am adding what value railway gives in settings so i dont thingk so its typo error.

Wait for at least 24 hours for txt verification. If it doesn't verify, then remove and re add your domain as mentioned in previous response.

Start by checking whether the TXT record has actually propagated.

Run:

dig TXT book.lavuedemer.com

or use a public DNS checker. If the verification TXT record doesn't appear there, Railway won't be able to verify it either.

If it does appear, verify that:

The Host/Name matches exactly what Railway expects.

The TXT value is an exact match (no extra quotes or spaces).

You don't have multiple TXT records for the same host that could interfere with verification.

If all of that looks correct, share a screenshot of your DNS records (you can hide sensitive values). That should make it easier to spot whether it's a DNS configuration issue or something else.

On hostiger it is showing me two TXT records. One for railway and other @ with outlooks and on dns checker it shows me values of outlook not the railway value. Addiotionaltionally hostinger doesn't allow me cname so i added alias, whoch shows verified status on railway.

Did you remove the domain from Railway or did you only delete the TXT record?

It is common to use an alias for the CNAME part as you mentioned hostinger doesn't allow direct CNAME at root. But txt is independent to be resolved cleanly.

In your hostinger DNS records, look for the railway txt record at @/root level which usually has a host/name as " _railway-verify"

Make sure host/name matches exactly with railway provided txt.

Delete any other conflicting or duplicate txt records as multiple txt records at the same host can cause the verifier to pick the wrong one.

Also manually verify the propagation using dnschecker.org

i deleted the txt record and then added it again.

After checking your screenshot, you should follow this response.

Wait a few more hours.

If it stays stuck, then remove the domain and re-add DNS records provided by railway

From the screenshot, the DNS record looks mostly correct, but remove the quotes around the TXT value if Hostinger added them automatically. It should be:

railway-verify=...

not:

"railway-verify=..."

After saving, check that the record has propagated:

dig TXT _railway-verify.book.lavuedemer.com

or use a public DNS checker. If the record is visible there but Railway still shows Pending, share the CNAME record for book.lavuedemer.com as well. That will help verify that both records match what Railway expects.