Everyone who has ever pointed a custom domain at Vercel knows the ritual. You deploy the project, add the domain in the panel, and get handed a CNAME to paste into some DNS zone. Then comes the wait for verification, the typo in the record, the second wait. The project was live in ninety seconds; the name took an evening. And for our users the ritual had an extra verse, because a free domain that still needs a hand-wired binding is not quite free yet.
Today the ritual ends. Every free PFS suffix now supports one-click binding to Vercel projects, with no manual DNS records for verification or attachment. It is live as of November 21, 2026 for bg5.net, is-a.si, nastu.net, us.mw, fs.kg, and pfsdns.org.
The new flow
The order is the interesting part: deploy first, claim the name after.
- Deploy your project on Vercel exactly as you always have;
- Apply for your free domain in the domain console, same checks as always;
- Bind it to your project in one click and start visiting. No records to paste, no verification queue, no waiting for propagation. Your site is live on your own name, https and all.
Why we call it inheritance
The records you used to paste by hand still matter; they just stopped being your problem. They are placed automatically as part of the binding, and verification and attachment happen inside the same click, so a fresh domain inherits its place on Vercel the moment it exists instead of earning it record by record.
The same holds for a name you have been holding for a while: the bind works exactly the same way in the console, one click, no archaeology in old DNS settings.
Who this is for
Frontend folks shipping on Vercel every week, students putting a portfolio behind a name that looks real on a CV, and anyone who ever abandoned a custom domain because the binding steps ate the motivation the deploy had generated. The project part you already know how to do. Now the name part costs one click too.
Thank you
The pieces keep snapping together: a free name, DNS that needs no second signup, hosting when you want a server, certificates that renew themselves, and now a straight wire into the platform most of you deploy on first. If you bind a domain to a project, show us in SEUS Community with the #PFS tag: we read everything, and someone in that thread is one deploy away from their own site. And if PFS keeps being useful to you, a star on GitHub helps the next builder find the whole stack.