7 days ago
I purchased inonpizzahouse.com through Railway and attached it to blissful-benevolence in the adventurous-prosperity project (production).
Railway DNS shows ANAME @ -> 8nn81o7a.up.railway.app. The domain status is verified and the certificate is valid, but the website fails with DNS_PROBE_FINISHED_NXDOMAIN.
The command "nslookup inonpizzahouse.com ns1kpv.name.com" reaches the authoritative nameserver but returns no IP address. The target 8nn81o7a.up.railway.app resolves to 69.46.46.127.
Please investigate why the Railway-managed ANAME is not publishing an A record.
3 Replies
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
You're right: the ANAME for inonpizzahouse.com is configured correctly, but our DNS provider’s nameservers aren’t returning the corresponding A record. Your certificate is valid, and your application responds when we bypass DNS. We’ve escalated this for investigation, and there’s nothing you need to change right now. We’ll get back to you as soon as we have more information. I’m sorry this is keeping your site inaccessible.
Status changed to Awaiting User Response Railway • 7 days ago
7 days ago
npm install -g @railway/cli && railway login
Status changed to Awaiting Railway Response Railway • 7 days ago
Status changed to Awaiting User Response sam-a • 7 days ago
6 days ago
The cause was a bug at our upstream DNS provider, and it has now been fixed. Your domain's root now resolves to our edge from public DNS, so please try loading the site again.
If you still see DNS_PROBE_FINISHED_NXDOMAIN, your device or resolver may have cached the old empty answer, and it will clear once that cache expires.