Hey everyone, posting here after going through Vercel’s support chat and hitting a wall on the Hobby plan. Hoping someone from the Vercel team picks this up as the issue seems to be on Vercel’s side rather than anything I’ve misconfigured.
The situation
I purchased mofu-notebook.kitchen directly through Vercel three days ago. The domain works fine from my location (Amsterdam) but returns DNS_PROBE_FINISHED_NXDOMAIN in the UK and several other regions. Confirmed via whatsmydns.net which shows clear red X’s in the UK, Dallas TX, and Mexico City while the rest of the world resolves correctly.
What the evidence points to
I ran the vercel-debug.sh diagnostic from Vercel support. The key findings are that all 8 Vercel edge IPs return HTTP 200 with valid SSL when bypassed directly — so the infrastructure itself is completely healthy. The issue is purely at the DNS resolution layer. The dig +trace is where things get interesting: it terminates abnormally after receiving only 50 bytes from i.root-servers.net and never reaches the .kitchen TLD nameservers or Vercel’s authoritative nameservers. A healthy trace should show the full chain from root → .kitchen TLD → ns1/ns2.vercel-dns.com → A records.
On top of that, the Vercel dashboard shows a warning triangle 
next to “Vercel” in the Nameservers column on the domain management page — which is what caught my attention in the first place.
What Vercel support said
The support chat acknowledged the diagnosis and said — and I’m paraphrasing here — that because this is a Vercel-managed domain, the registry relationship with Identity Digital is handled internally and I cannot contact them directly. The bot agreed three days is longer than typical propagation time and that it warrants investigation into whether the NS delegation was fully committed at the registry. It then tried to open a support case but hit a wall because that requires a Pro plan.
The thing is, this isn’t a DNS configuration question — I didn’t misconfigure anything. Vercel is the registrar, Vercel set the nameservers, and the evidence suggests the NS delegation at the .kitchen registry level may not be fully committed. That feels like something that should be covered regardless of plan tier.
Would really appreciate if someone from the Vercel team could take a look and verify the NS delegation status for mofu-notebook.kitchen with Identity Digital. Happy to share the full vercel-debug.txt output if helpful.
All the best, Jef
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.
You can also use v0 to narrow down the possibilities.