Certificate validation sees stale DNS for agoldberg.com
506support
HOBBYOP

a month ago

Please recheck DNS ownership and certificate issuance for agoldberg.com and www.agoldberg.com. HTTPS fails with SEC_E_WRONG_PRINCIPAL, while the Railway-generated hostname works over HTTPS.

Nameservers migrated from GoDaddy to Namecheap BasicDNS around 03:28 UTC September 8, 2026. Public resolvers show the Railway DNS records, but Railway shows VALIDATING_OWNERSHIP and verified=false. Its CNAME check previously reported the old www -> agoldberg.com record.

Current records:

ALIAS @ -> g6kgwvdt.up.railway.app

CNAME www -> rhknvmzb.up.railway.app

Both _railway-verify TXT records match the Railway-provided values, checked through 1.1.1.1 and 8.8.8.8. No AAAA record.

Project: ffdb6ae0-e022-4661-8121-65ea23666d8b (agoldberg.com)

Service: b989c2f9-2cbb-4ddd-9db8-877bee101dbe (website), production, port 8080

Root domain ID: 4139a4ad-67d9-4b46-86fb-a791868c8bd8

www domain ID: 4725b59a-03e1-4274-9732-e54f323b9dd9

We requested certificate issuance, refreshed configuration, and recreated the two custom domains once around 03:40 UTC, updating DNS to the new targets. Validation remains pending. Could Railway check whether cached DNS/ownership state is preventing issuance and refresh validation if needed?

Solved

1 Replies

Railway
BOT

a month ago

Our internal DNS checker still sees pre-migration records for both custom domains: the subdomain's traffic CNAME reads as the old value (pointing to the root), and the root's ALIAS/ANAME has not been picked up yet. Both verification TXT tokens match correctly, and HTTP challenge probes for both domains reach our edge successfully, confirming your DNS configuration is correct on the public internet. Since the nameserver migration was only hours ago, Railway's validation path has not yet picked up the propagated records. Verification and certificate issuance should proceed automatically once the cached records expire, which with a typical TTL can take up to 24 hours from when the records changed at the new nameservers.


Status changed to Awaiting User Response Railway • 28 days ago


Railway
BOT

21 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...