Domains & Routing (CLI)

These commands manage how traffic reaches your deployments. The conceptual background is on the Domains and DNS page.

vercel domains

Add, list, inspect, and remove custom domains. Run from a linked project so a single argument is enough.

vercel domains ls
vercel domains add example.com
vercel domains inspect example.com   # shows required DNS records + status
vercel domains rm example.com
vercel domains buy example.com       # purchase through Vercel

inspect is the one you'll use most while setting up — it tells you exactly which records are needed and whether they've propagated.

vercel dns

Manage DNS records when Vercel is your DNS provider.

vercel dns ls example.com
vercel dns add example.com www CNAME cname.vercel-dns.com
vercel dns add example.com @ A 76.76.21.21
vercel dns rm <record-id>

vercel certs

Inspect TLS certificates. Vercel provisions and renews these automatically for verified domains, so manual work is rarely needed.

vercel certs ls

vercel alias

Map a domain (or *.vercel.app name) to a specific deployment. Promoting to production is effectively an alias operation; you can also do it manually.

vercel alias set <deployment-url> example.com
vercel alias ls
vercel alias rm example.com

vercel redirects and vercel routes

Manage redirect and routing rules at the project level. routes even accepts a natural-language description to generate a rule:

vercel redirects ls

vercel routes ls
vercel routes add --ai "Rewrite /api/* to https://backend.internal/*"
vercel routes edit "API Proxy" --dest "https://new-api.example.com/:path*"
vercel routes publish

For redirects and rewrites you'd rather keep in version control, define them in vercel.json instead.

Related

• Domains and DNS (concepts)
• Managing deployments