Custom domain routing returns 404 (unable to resolve dns name <domain>.internal) #1399

Description

Custom domain routing returns 404 even though DNS validates as configured.

• Deployment: deploy_058d7ad7654c230a1aa2d7b13d95b329
• Project: proj_033002ed7c0a3fe9d42c91ce1e137e3f (pittsventures)
• Org: org_37ED0plxQJQuvlgAn66YzGxdjcD

Vanity URL works (HTTP 200)

https://pittsventures-ethan-s-team-1766459116.agentuity.run

Custom domains return 404 from the Agentuity edge

• https://pittsventures.com → 404 with header x-agentuity-err: unable to resolve dns name pittsventures.com.internal
• https://www.pittsventures.com → 404 with header x-agentuity-err: unable to resolve dns name www-gcpuse1-k57b.pittsventures.com.internal

Diagnostics

bunx agentuity project domain check reports both domains as [OK] Configured:

Domain:  pittsventures.com
CNAME:   p0469f06d890a8493.agentuity.run
A:       35.185.91.57
Status:  [OK] Configured

Re-running bun run deploy (agentuity deploy) does not resolve the issue — validate-custom-domains step passes on the CLI side, but the edge still cannot resolve the internal service name.

This looks like a missing internal DNS / service registration for the custom domains on the edge proxy side. The deployment itself is healthy; only the custom-domain binding is broken.

Environment

• CLI Version: 1.0.30
• Bun Version: 1.3.6
• Platform: darwin (arm64)

Report

• Report ID: e48754f60b0b7b39eb6df35a6189ef8a
• Report Logs: https://agentuity-log-reports.t3.storageapi.dev/e48754f60b0b7b39eb6df35a6189ef8a.zip

Automated report generated by agentuity support report