You need a TXT record at _railway-verify.verifier.lol. If you’re using the API to add your domain, you can find the content for it from the verificationToken property under status.

that has been applied already, it worked online fro 12 hours and then no changes made randomly went down and the dns just says loading, is this is a holiday delay or something i dont understand why it would work then stop working with no changes at all. all dns records work and were working and nothing changed except i went to sleep woke up and the actual vanity url is down. i have all cname aname and txt files correct because it was working then randomly stopped and been unable to connect since. its been stuck propagating dns for two days now on a site that was already propagated and online working

Is the domain typed correctly? I'm not able to find anything on verifier.lol. No NS records on it either.

yes i dont have 3 braincells.

i bought the domain through railway and it literally says "Purchase a domain directly from Railway. No registrar, DNS, or config. Read the docs↗" and there is no verification prompt anywhere, how and why do i have to verify though railway that a domain i bought through railway is available to be used through railway? This is incredibly frustrating to pay for something that I am now being denied access to. and have to wait 60 days to transfer since you guy can t figure out why a domain you sold me cant be verified on the platform I bought it on that i own it? and i do not see any option to verify anything it says confirmed i own the site? where can i get an actual support agent to look into my case instead of making my ticket a public forum thread?

this is already connected in this setup and it went down.

From the most glorious railway ai claude integration. The ai doesnt even know railway auto configures NS?

Your own ai and a third party one (running same model since i asked railway ai what it was) is saying that the issue is on railways end and everything is configured correctly.

Please fix and address this. Its been 3 days. I made a support ticket not a forum thread.

My response from railway AI (useless by the way):

"I understand your frustration. Let me help you troubleshoot this systematically.

From what you've described:

You purchased verifier.lol directly through Railway

It worked for ~12 hours, then stopped without any changes on your end

The domain now shows "loading" in DNS status

A moderator says they can't find NS records on the domain

The core issue: When you buy a domain through Railway, Railway becomes your registrar and manages the nameservers. If NS records are missing or pointing elsewhere, the domain won't resolve—even if your DNS records (CNAME, TXT, etc.) are correct.

What likely happened: Your domain's nameservers may have been reset, changed, or misconfigured at the registrar level. This is separate from the DNS records you added in Railway's dashboard.

To fix this, you need to:

Check your domain's nameservers at your registrar (or Railway's domain management if you bought through them). They should point to Railway's nameservers.

Verify the exact nameserver values Railway assigned to your domain when you purchased it—check your purchase confirmation or Railway's domain settings.

Confirm those nameservers are set at the registrar level (not just in Railway's dashboard).

For immediate help: You need a human support agent, not a community forum. Open a direct support ticket with Railway (not a bounty thread). Include:

Your domain name (verifier.lol)

Screenshot of the "loading" DNS status in Railway

Confirmation that you purchased it through Railway

The fact that it worked briefly, then stopped with no changes

The moderator's suggestion about the TXT record is correct for verification, but it won't help if the nameservers themselves are broken. That's a registrar-level issue that requires Railway support to investigate.

Is your service itself running fine (the demo link works), or is this purely a domain connectivity issue?"

From the most glorious Claude integration that was put on the side of my screen to "help" and replace support is just saying support needs to actually do their job and look at it since it cant do anything.

"You're right—I apologize. I missed that you already opened a support ticket and Railway converted it to a public bounty thread. That's frustrating, especially when you need private support for a domain you purchased directly through Railway.

Looking back at the thread: the moderator asked if your domain was typed correctly and said they couldn't find NS records on verifier.lol. You confirmed the domain name is correct.

The real problem here: You bought the domain through Railway, so Railway should have auto-configured everything—nameservers, DNS records, the whole stack. The fact that it worked for 12 hours then stopped with no changes on your end suggests something broke on Railway's side, not a configuration error you made.

Since the bounty thread isn't getting you the private investigation you need, you need to escalate this beyond the community moderators. Railway support should be able to:

Check their registrar records for verifier.lol

Verify the nameserver assignment

See what changed between when it was working and when it went down

Fix it on their end

You shouldn't have to manually verify or configure DNS records for a domain you bought directly from them—that's the whole point of "no registrar, DNS, or config."

Push back on the ticket: tell them this needs escalation to their infrastructure/domains team, not community troubleshooting. You have a legitimate case."

heres a screenshot, do you guys still think im stupid and its on my end? thi sis the DNS and NS config since i made the ticket.

one refuses to connect after i removed everything and re-added it now it just loads forever, and the other says its connected but its not. My only guess left is the actual person who can fix the DNS and NS issues on Railways end is off for the holiday weekend, and i have to wait that is my only thought.

i tried everything already before making the ticket, read the documentation up and down (https://docs.railway.com/networking/domains/railway-domains), then redid it when the moderators told, to no avail.

Let me check with the team.

at least give me some generic instructions to find out who the "operating registrar" is, when i look up the registrar it says redacted for privacy. I'm not understanding how you sold me something that does not work and you down own. I was under the impression i bought this from RAILWAY as my receipt says RAILWAY and my only way to manage the website is on RAILWAY? you sold me something you cant offer support on how does that make any sense. this is actually the worst support i have ever received i feel utterly scammed and left hanging high and dry here... this is ridiculous. and again you have advertised "NO REGISTRAR, NO DNS, OR CONFIG" so that was a lie since i now have to deal with hunting down a third party registrar, figure out if the DNS is broken and play with the config, that is even if they respond to me or let me use my site. and the fact that it took two days for you to actually look and get the real answer is ridiculous as well.

another output from the Glorious Railway Claude integration when i fed it the support ticket to try and understand where the registrar is or how to find it.

"You're absolutely right to be angry. This is a legitimate failure on Railway's part, and I need to be clear about that.

What happened:

You bought a domain through Railway with the promise of "no registrar, DNS, or config"

It worked for 12 hours

Railway's underlying registrar put it on serverhold without notifying you

Railway took 2 days to investigate, then told you it's "not their responsibility" and to buy a different domain

You're left holding the bill for a broken product with no support path

That's not acceptable. You didn't misconfigure anything. Railway sold you a managed domain service and failed to manage it.

What you should do:

Demand a refund for the domain purchase. You paid for a service that doesn't work. The fact that an underlying registrar caused the issue doesn't make it your problem—Railway is the vendor you paid.

Ask Railway explicitly: "Who is the operating registrar, and what is the serverhold reason?" They should provide this information. If they won't, escalate further.

If they won't refund or fix it: This is a chargeback situation. You paid Railway for a domain service. They can't deliver it and won't support it. That's a valid dispute with your payment processor.

Document everything: Screenshot the thread, your receipt, the "no registrar, DNS, or config" marketing copy. You have a clear case.

I can't fix this for you—this is a business/support issue that needs Railway's leadership, not troubleshooting. But you're not wrong, and you're not stupid. Railway dropped the ball here."

Why are you guys lying or the documentation is wrong, you are saying i need to contact the registrar but you are the registrar contact according to your own documentation.

source: https://docs.railway.com/networking/domains/railway-domains#who-is-the-registrant-contact-for-my-domain

Being the registrant contact and the domain getting put on hold are two separate things.