Custom domain add fails with false "DNS not configured" error (reproducible across CLI v3 and v8, and Console UI)

[takaa1004]

Hi Prisma team,

I'm unable to register a custom domain on my Compute app due to what appears to be a backend bug, not a DNS misconfiguration. I've already filed CLI feedback reports but wanted to escalate directly since this is fully blocking my launch.

Account / resource identifiers

Workspace: Personal workspace (id: cmt890yh30zb33rdverov6xnx)
Project: Brave Orange Cygnet (id: proj_cmt891ao80fwryoe3denbhlox)
App / Service: parking-smoking-finder (id: cps_gkm52k96bkxrsiucj9f7wak6)
Live URL: https://gkm52k96bkxrsiucj9f7wak6.nrt.prisma.build/
Domain I'm trying to add: www.parksmoking.com (and parksmoking.com)

What I did

Set DNS: www.parksmoking.com CNAME → switchboard.nrt.prisma.build (via Cloudflare, DNS-only/unproxied). Also set the apex parksmoking.com to CNAME-flatten to the same target.
Verified this DNS record independently against three public resolvers (1.1.1.1, 8.8.8.8, 9.9.9.9) — all return switchboard.nrt.prisma.build. correctly and consistently, and have done so continuously for 2+ days (checked repeatedly since 2026-08-25).
Ran app domain add www.parksmoking.com --project proj_cmt891ao80fwryoe3denbhlox --app parking-smoking-finder --branch main (CLI 3.0.0-beta.30).
Expected result: domain registers, or at minimum a DNS check that reflects the actual DNS state.

Actual result: DOMAIN_DNS_NOT_CONFIGURED — "DNS is not configured for www.parksmoking.com. Ensure the hostname CNAMEs to switchboard.nrt.prisma.build." — despite the CNAME being correct the entire time.

Cross-checked on the new CLI (8.0.0-rc.10): same failure pattern, but with a different, more diagnostic error. service show parking-smoking-finder --project proj_cmt891ao80fwryoe3denbhlox correctly resolves and returns the service. But service domain add www.parksmoking.com --service parking-smoking-finder --project proj_cmt891ao80fwryoe3denbhlox (and service domain show too) fails with:

SERVICE.SELECTION_INVALID — "The requested service does not exist in the resolved project" — "The service "parking-smoking-finder" could not be found in resolved project "proj_cmt891ao80fwryoe3denbhlox"."
This happens whether I pass the service by name or by id (cps_gkm52k96bkxrsiucj9f7wak6). Every non-domain service subcommand (list, show, open) resolves the exact same service correctly.

Also reproduced identically in the Prisma Console UI (not just CLI): adding www.parksmoking.com manually via the Console's domain-add flow gives the same "Couldn't add domain — DNS is not configured..." message, even though the Console itself displayed the correct expected CNAME target.

Conclusion: this looks isolated to whatever resolution/verification code path the domain-add (and domain-show) mutation hits — not DNS, not general service/project resolution, and reproducible across two CLI major versions and the web Console.

Prior CLI feedback IDs for this issue (same underlying bug, submitted while investigating):

01a03811-fa7a-7000-90d9-e48950d305a5
01a03829-f29c-7000-9c3c-0cf0f3155189
01a03b3c-2d50-7000-a0a1-76b3ba8d80f2
01a03b66-d3ed-7000-a992-78301327c54a
This is currently blocking me from launching on a custom domain. Any help figuring out why the domain-add path can't resolve a service that every other command finds fine would be greatly appreciated.

Thanks!

[takaa1004]

Still reproducing 2 days later — re-verified just now (2026-08-27 23:43 UTC).

DNS is unchanged and still correct, across three independent public resolvers:

$ for r in 1.1.1.1 8.8.8.8 9.9.9.9; do dig @$r +short CNAME www.parksmoking.com; done
switchboard.nrt.prisma.build.
switchboard.nrt.prisma.build.
switchboard.nrt.prisma.build.
The command still fails identically (CLI 8.0.0-rc.10):

$ prisma service domain add www.parksmoking.com
--project proj_cmt891ao80fwryoe3denbhlox --service parking-smoking-finder --json

SERVICE.SELECTION_INVALID — "The requested service does not exist in the resolved project"
To restate the part that seems most diagnostic: every other command resolves this exact service without issue. prisma service list and prisma service show parking-smoking-finder both return it correctly (cps_gkm52k96bkxrsiucj9f7wak6, live, region ap-northeast-1) with the same --project value. Only the service domain * subcommands claim it doesn't exist — and passing the service by id instead of name makes no difference.

So there appear to be two separate symptoms of what may be one underlying problem:

On CLI v3 (app domain add) and in the Console UI: DOMAIN_DNS_NOT_CONFIGURED, despite correct DNS.
On CLI v8 (service domain add): SERVICE.SELECTION_INVALID, despite the service resolving fine everywhere else.
Is there anything I can run to help narrow this down — a debug/verbose flag that shows which resolver or which project/branch scope the domain-add path is actually using? Happy to gather whatever would help.

This is still fully blocking a custom-domain launch, so any pointer would be much appreciated. Thanks!