Resend DNS records added at the wrong provider (nameserver conflict)

TL;DR: You add the records at Cloudflare but nothing verifies because your DNS is actually managed at Vercel or your registrar. When DNS is split across providers, the records must go where the nameservers point. Confirm the cause: your domain's DNS may be managed in multiple places (registrar, Vercel, Cloudflare), and you may be adding records at the wrong one. Check: run a nameserver lookup for your domain with a tool like dns.email and note which provider actually controls DNS.

The error

text
records are correctly entered at your DNS provider, propagation time has passed, but Resend still shows them missing.

The fix

TL;DR: You add the records at Cloudflare but nothing verifies because your DNS is actually managed at Vercel or your registrar. When DNS is split across providers, the records must go where the nameservers point. Confirm the cause: your domain's DNS may be managed in multiple places (registrar, Vercel, Cloudflare), and you may be adding records at the wrong one. Check: run a nameserver lookup for your domain with a tool like dns.email and note which provider actually controls DNS.

The error

records are correctly entered at your DNS provider, propagation time has passed, but Resend still shows them missing.

The fix

1. Confirm the cause: your domain's DNS may be managed in multiple places (registrar, Vercel, Cloudflare), and you may be adding records at the wrong one. What matters is which provider the domain's nameservers point to, not where you usually edit DNS.
2. Check: run a nameserver lookup for your domain with a tool like dns.email and note which provider actually controls DNS.
3. Fix: add the Resend records at that provider. If you already added them elsewhere, either move them or change the nameservers so the provider holding the records is authoritative.
4. Verify: check the records publicly with nslookup (nslookup -type=TXT on the DKIM name, -type=MX on the send subdomain) before trusting any provider's panel. Then use "Restart verification" in the Resend dashboard.
5. If the records are publicly visible but Resend still fails them after 24 hours, contact Resend support with your domain name and screenshots of your DNS configuration.

When to use this

• You are seeing this exact error message; match the block above, not just part of it.
• The failing call matches the scenario in the title: Resend DNS records added at the wrong provider (nameserver conflict).
• You want the fastest verified fix before digging through logs.

When not to use this

• Your error text differs from the block above; close cousins often have different causes.
• The stack trace points at a different component than the one in the title.
• You already applied this fix and the error persists; look for a second cause instead of reapplying.

Compatibility

• Not pinned to a specific version; follows current Resend behavior.

Documented in Resend knowledge base: DNS managed in multiple places means records may be added at the wrong provider; check the real nameservers with a lookup tool like dns.email; DNS changes can take up to 72 hours; use Restart verification; after 24 hours of failure contact support with domain and screenshots. Evidence: resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying.