Connect a Free Subdomain to Vercel

Table of Contents
AICLUB's live catalog goes beyond .ai.id, with .web.id, .cv, .eu.cc, and more base domains in the domain catalog.
AICLUB uses DNS-only (grey cloud) for the CNAME record to Vercel, Netlify, and other static hosts. Do not enable the Cloudflare proxy on that record: the target platform terminates TLS itself, and proxying can cause SSL or routing conflicts.
Pointing a subdomain means publishing one DNS record that tells browsers where a named address should go. For example, portfolio.aiclub.ai.id can point to a Vercel deployment while a different subdomain points to a VPS. The key is matching the record type to the destination your platform documents.
What do you need before adding a record?
First deploy the site on its hosting platform. Then open the platform’s custom-domain settings and copy its recommended DNS value. Do not guess a CNAME target from another project: providers can use different validation names or update their instructions. Finally, decide the subdomain name you want visitors to use.
How do you point a subdomain to Vercel?
- Deploy the project and add the intended subdomain in Vercel’s domain settings.
- Copy the exact CNAME target Vercel shows for that project.
- In AICLUB, claim the name with the CNAME routing type and paste that target.
- Return to Vercel and wait for its domain verification before testing HTTPS.
Which record should each platform use?
| Destination | Record | What to enter |
|---|---|---|
| Vercel | CNAME | Target shown by Vercel |
| Netlify | CNAME | Target shown by Netlify |
| Cloudflare Pages | CNAME | your-project.pages.dev |
| VPS / own server | A | Public IPv4 address |
CNAME or A record: what is the difference?
A CNAME names another hostname, so it suits platforms that manage their own destination infrastructure. An A record is a numeric public IPv4 address, so it suits a VPS or server you administer. Never put a URL, slash, or page path into either field: a DNS record needs only the target host name or IP address.
Read Vercel’s official domain guide.
What problems are common after DNS is added?
- The CNAME target does not exactly match the value provided by the host.
- The platform domain was not added or verified in the hosting dashboard.
- A record was used for a host that requires a CNAME.
- A resolver is still using a cached DNS response.
Check the DNS target first, then check the platform’s domain status. Propagation can differ between networks, so test after the provider says verification is complete. For a general explanation of record behavior, see Cloudflare’s official DNS record documentation.
Read the Cloudflare DNS record reference.
How to confirm a Vercel custom domain is ready
After creating the record, the Vercel dashboard is the main source of truth. Do not replace a CNAME only because one device still shows an old page. Check that the subdomain was added to the correct project, whether Vercel requests extra verification, and whether the deployment is active. If a project uses preview deployments, make sure the production domain points to the production deployment visitors should open.
Frequently asked questions
Which record points a subdomain to Vercel?
Use the exact CNAME target shown in the Vercel project’s domain settings.
When should I use an A record?
Use it when the destination is a public IPv4 address, usually a VPS or server you manage.
Why is it not live immediately?
Check the target and platform verification, then allow resolver caches time to update.
Does a Vercel subdomain need to be added in the Vercel dashboard?
Yes. Add the intended domain to the correct Vercel project, then follow the DNS target and verification status Vercel displays.
Continue learning
Ready to point your project?
Claim a free, no ads subdomain for a legitimate website or app.