DNS manual re-check
vojtech-petru
PROOP

2 months ago

Hi,

I'm setting up a custom domain for my Web service and need a manual DNS verification trigger.

Project Details:

  • Project: inomech
  • Service: Web
  • Custom Domain: shop.inomech.tech

DNS Status:

  • CNAME record: Verified
  • TXT verification record: ⏳ Pending

TXT Record Verification:

The _railway-verify.shop.inomech.tech TXT record is live and correct. Here's the verification:

nslookup -type=TXT _railway-verify.shop.inomech.tech
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
_railway-verify.shop.inomech.tech text = "railway-verify=0d90f16607c034235279bb34b6755b29b0760da66e225175f4ba271435a0eacf"
Authoritative answers can be found from:

The record is propagated and accessible, but Railway's automatic validation hasn't picked it up yet. Could you please manually trigger a re-verification check on your end?

Thanks!

Solved$10 Bounty

Pinned Solution

I'd recommend removing the related DNS records from both Railway and your DNS provider, then re-adding the records after 10-15 minutes.

7 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


sam-a
EMPLOYEE

2 months ago

Your DNS records are both correctly configured and fully propagated. The CNAME points to the right target and the TXT verification token matches. Try removing the custom domain from your service settings and re-adding it to trigger a fresh verification cycle. Avoid repeating this more than once, as Let's Encrypt enforces rate limits on certificate issuance (5 per domain per week).


Status changed to Awaiting User Response Railway about 2 months ago


vojtech-petru
PROOP

2 months ago

Hello Sam,

will the re-add create a new DNS record values? I'm not managing the DNS settings unfortunately, and lets say the guy who does is not very quick. I'd very much appreciate if I didn't need to contact him with an update, as that would set me back for at least a week.


Status changed to Awaiting Railway Response Railway about 2 months ago


Railway
BOT

2 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway about 2 months ago


vojtech-petru

Hello Sam, will the re-add create a new DNS record values? I'm not managing the DNS settings unfortunately, and lets say the guy who does is not very quick. I'd very much appreciate if I didn't need to contact him with an update, as that would set me back for at least a week.

I'd recommend removing the related DNS records from both Railway and your DNS provider, then re-adding the records after 10-15 minutes.


vojtech-petru
PROOP

a month ago

Thanks for making the thread public without a proper answer for an issue where outsiders can't help.

For the record, this is a second time I've contacted Railway support with a bug and second time I've got no help.


(Have you tried what I suggested above?)


vojtech-petru
PROOP

a month ago

I've removed and added the same domain and it generated the same DNS records. So everything works now.

I apologise for being a bit mad, but nobody answered my original will the re-add create different DNS record values? question. Now I know the answer.


It just helps avoid any one-off caching issues regarding the DNS servers, but good to know it worked.


Status changed to Open 0x5b62656e5d 16 days ago


Status changed to Solved 0x5b62656e5d 16 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...