Connect a Free Subdomain to Netlify
Table of Contents
- What you need
- Step 1: get the Netlify address
- Step 2: add the name in Netlify
- Step 3: create the CNAME record
- HTTPS and the first visit
- Troubleshooting
- Frequently asked questions
- Is Netlify free?
- How long does DNS take?
- Can several subdomains point to one Netlify project?
- Netlify custom domain: final checks
- Frequently asked questions
- Continue learning
AICLUB's live catalog goes beyond .ai.id, with .web.id, .cv, .eu.cc, and more base domains in the domain catalog.
TL;DR. Three checks make this work: add the name in Netlify first, copy its DNS target, then create the CNAME in AICLUB.
AICLUB uses DNS-only (grey cloud) for the CNAME record to 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.
What you need
You finished a site and it is sitting on a long Netlify address. That works, but it is hard to say aloud and easy to mistype. A subdomain gives the project one stable public name. The job has two parts: add the name in Netlify first, then tell AICLUB where traffic should go.
Have the Netlify project open in another tab. You also need one claimed AICLUB subdomain and permission to edit its DNS target. Do not guess the hostname. Copy the exact value that Netlify shows. A small spelling error can look like a DNS problem for hours.
Step 1: get the Netlify address
Publish the project once and find its default address. For this setup, the DNS destination is your-site.netlify.app. Keep the project published while you connect the name. A deployment that is paused, deleted, or protected behind a login will not become a useful public destination.
Important: Add the subdomain in Netlify before creating the CNAME record in AICLUB. See the official Netlify documentation (setup order checked November 3, 2026). The panel instructions below explain how.
Step 2: add the name in Netlify
In Netlify, open Domain management for the site and add the full custom domain. Netlify will check the DNS record before serving the site under that name. This step matters because DNS alone does not grant a project permission to answer for your address. The dashboard may show a verification state first. Wait for it to see the CNAME, then set the name as the production domain only when the project preview is correct.
Step 3: create the CNAME record
Open the claimed subdomain in AICLUB and choose a CNAME route. Put the destination value in the target field: your-site.netlify.app. A CNAME says that your public name follows the hostname supplied by the hosting platform. It is the right record for a normal hosted subdomain. Do not add https://, a path, or a trailing page name.
For Netlify, set the DNS record to DNS-only (grey cloud), not Proxied. Proxying can conflict with Netlify SSL or routing. DNS can appear quickly, but browsers, resolvers, and the host each keep their own cache. Check the exact hostname instead of repeatedly changing the record.
HTTPS and the first visit
Netlify can provision a Let’s Encrypt certificate after DNS and domain ownership checks succeed. Let the platform finish the process rather than creating a second, conflicting record. Do not work around a certificate warning by disabling HTTPS or changing the target to an IP address. Certificate issuance needs the hostname to resolve consistently. Once the host reports that the certificate is ready, open the subdomain in a fresh private window and test a real page, not only the homepage.
Troubleshooting
Certificate provisioning can pause when the CNAME target differs from the site name. An apex-domain guide does not apply to an AICLUB subdomain: use the CNAME target Netlify provides. If the site is not found, confirm the domain was added to this exact site, not another team project. Start with the record value, then the custom-domain setting, then the deployment status. Those three checks solve most cases. An error page from the host usually means DNS reached the host but the host has not linked the name to the right project. A DNS error usually means the CNAME is absent, misspelled, or still cached.
If you are choosing a host, compare the Cloudflare Pages guide, the Netlify guide, and the Vercel guide. The DNS pattern is similar, but each dashboard names the custom-domain screen differently. Before you start, review what a subdomain is; it makes the record choices less mysterious.
Frequently asked questions
Is Netlify free?
Netlify offers plans and limits that can change. Check its current product page. The DNS connection itself does not require a separate AICLUB fee for a free subdomain.
How long does DNS take?
The route can become visible quickly, but caches and certificate checks can take longer. Give the host time to verify before changing a correct record.
Can several subdomains point to one Netlify project?
Usually yes when the project and hosting plan allow multiple custom domains. Add each name in Netlify and create one matching DNS route for each.
Ready to give your project a shorter address? claim a free subdomain. After it is live, link to this guide or the Cloudflare Pages guide from your project notes so the next setup takes less time.
Netlify custom domain: final checks
Add the subdomain in the Netlify dashboard and copy the CNAME target shown there. Do not enter a full URL or path in a DNS record. Once verified, test the page in a private window and use the same production URL in your README or portfolio.
Frequently asked questions
Which record should I use for Netlify?
Use the exact CNAME target Netlify shows for the domain.
Why is the domain not active yet?
Check the Netlify project, CNAME target, and verification status before changing records again.
Is HTTPS automatic?
Wait for Netlify to complete domain verification and issue the certificate before sharing the URL.
Can one project use multiple subdomains?
Yes, if the Netlify project and plan support multiple custom domains.
Continue learning
Ready to point your project?
Claim a free address for a legitimate project.