yes, this can be normal. Railway doesn’t just check if the DNS record exists — it waits until _their own DNS resolvers_ see it pointing to the right place. Even if DNSChecker is all green and your provider looks correct, Railway may still be seeing cached/old data. The most common reasons: * **High TTL** (1h, 4h, 24h) from previous records → some resolvers keep the old value longer * **Wrong record type** (CNAME vs A / ALIAS, especially for root domains) * **DNSChecker ≠ Railway’s resolvers** — they don’t always update at the same time 6 hours is annoying, but still within a normal propagation window. What I’d check: * Hostname matches exactly (no missing `www`) * Record type matches what Railway shows * TTL is ≤ 300s (if possible) * Avoid deleting/re-adding the domain — that usually resets the wait If it’s still stuck after \~24h, then it’s worth opening a support thread. If you want, tell me whether this is a root domain or subdomain and which DNS provider you’re using — happy to take a look.

Thanks! It was just the missing "www"! :-) After I added it, the webpage was available within a minute.