# vercel domain verification failed nameserver conflict

## TL;DR
Decide whether Vercel owns the DNS (move nameservers to Vercel) or not (keep external DNS and verify with a TXT record). Check the domain is not attached to another Vercel project or team and remove it there, add the verification record if needed, and confirm verification in the Vercel dashboard.

```text
vercel domain verification failed nameserver conflict
```

## Use this when

- Vercel domain verification fails mentioning nameservers or conflicts
- The domain was previously used on another Vercel project or team
- Verification fails even though DNS looks correct

## Not for this skill when

- Slow DNS propagation after correct setup (wait, not a conflict)
- Vercel build or deployment failures (unrelated to the domain)
- SSL errors after successful verification (check the certificate status)

## Steps

### Step 1: Check current nameservers

Look up the domain's nameservers. Expected: you know whether Vercel or someone else currently serves the DNS.

### Step 2: Choose one DNS path

Either move nameservers to Vercel for full management, or keep external DNS and use Vercel's A/CNAME plus TXT verification. Expected: a deliberate choice, not a mix of both.

### Step 3: Clear competing claims

Search your Vercel projects and teams for the domain and remove it wherever it is attached besides the intended project. Expected: exactly one project claims the domain.

### Step 4: Add the verification record

If using external DNS, add the TXT verification record Vercel provides. Expected: the record is published and visible publicly.

### Step 5: Verify in the dashboard

Complete verification in the Vercel project settings. Expected: the domain shows verified and the site serves on it.

## Tool compatibility

Vercel custom domains; Vercel project and team settings; DNS nameservers and TXT records.

## Variant phrasings

### Variant 1

vercel domain verification failed nameserver

### Variant 2

vercel custom domain already in use another project

### Variant 3

vercel domain conflict verification txt record

## Why it happens

Vercel needs exclusive proof that you control the domain, and two things commonly block it. The first is a nameserver tug-of-war: the domain points at Vercel's nameservers in one place and an external DNS in another, so neither side's verification completes. The second is a stale claim: the domain is still attached to an old project or a former teammate's team, and Vercel will not let two projects own one domain. Both present as a generic verification failure, which sends people re-checking DNS records that were never the problem. Resolving it is administrative: one DNS owner, one claiming project.

## Edge cases / pitfalls

- Domain transfer locks and 60-day change windows can block nameserver moves; plan around them.
- Wildcard domains need DNS-level verification; the simple CNAME path does not cover them.
- Removing the domain from the old project first avoids the conflict entirely during migrations.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_s9yPm80C31LS_VKq8JyMIQ