⌘K
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
sam We need authoritative guidance for one files-based Preview deployment in an existing Vercel project. Required invariants: - Every existing configured, branch, member, and custom-domain alias must retain its current deployment throughout creation. - The new deployment must have only its immutable deployment URL and zero aliases. - No Production deployment or project-setting change is authorized. CLI 62.1.0 documents --skip-domain as Production-only. Is there a supported CLI, REST API, or project control that prevents all automatic alias assignment for Preview? Please specify the exact supported parameter, API/CLI version, and coverage of configured and generated aliases. If no such control exists, please confirm that limitation. We cannot validate this through a trial deployment or a deploy-and-rollback operation.
Amy Egan As you already saw in the documentation, `--skip-domain` is used with the `--prod` option. Branch deployments get their own branch domain that is automatically updated to the latest deployment from that branch. Each deployment also gets a unique URL. The unique deployment URL stays with that deployment, and a new one is assigned to the next deployment. If you need a fixed domain then I'd recommend using the unique generated URL. If you can explain more about the bigger picture for your situation, I might have some other ideas about how to accomplish what you need.
