I have updated my vercel nameservers to point to cloudfare. it has been more than 24 hours but they have not been propagated anywhere.
Hi Abhirup,
I’d first separate DNS records from nameserver delegation.
For Cloudflare to become authoritative, the nameserver change has to be made at the domain’s registrar, not just by adding/editing DNS records inside Vercel. You can check what the public DNS chain is actually seeing with:
dig NS yourdomain.com +short
dig NS yourdomain.com +trace
If the result still shows Vercel nameservers, then the parent registry/registrar has not switched the domain to Cloudflare yet. If it shows Cloudflare nameservers in +trace but some resolvers still show the old ones, then it is more likely resolver cache/propagation.
If the domain was registered through Vercel, the relevant place is the domain’s Nameservers section in the Vercel Domains dashboard:
One more thing to check: if DNSSEC was enabled before switching to Cloudflare, a stale DS/DNSSEC setup at the registrar can also make the domain look like it is not resolving correctly.
Can you share the domain name, or the output of dig NS yourdomain.com +trace with anything unrelated removed?