Service: @workspace/api-server, environment production.

I added www.hiveone.co.nz as a custom domain. Railway's "Configure DNS Records" dialog gave me two records to add:

CNAME: www → [railway-generated subdomain].up.railway.app

TXT: _railway-verify.www → railway-verify=[hash]

I added both at my DNS provider. Confirmed via whatsmydns.net and nslookup from multiple resolvers (including Google's 8.8.8.8) that both records are fully propagated globally and resolving correctly to the target Railway originally gave me.

Despite this, the domain has shown "Waiting for DNS update" in the dashboard for over 24 hours.

When I asked the in-dashboard AI agent to check, it told me the CNAME should instead point to a different, generic public networking URL for the service — not the one originally generated by the Configure DNS Records dialog for this specific custom domain. It also claimed the domain "is not in the service's domain configuration," which contradicts it visibly showing under Public Networking with a pending status.

Could someone check the actual custom domain verification state for this domain on this service? DNS is correct and propagated per the original instructions — I'd rather not change it again based on a possibly-incorrect agent suggestion and lose the propagation I already have.

Happy to share screenshots of the DNS records and nslookup output via DM if useful.