Subdomain setup guide

after DNS ACTIVE, connect this hostname at your destination platform

Important: DNS ACTIVE means AICLUB created the DNS record. The custom domain and HTTPS still need to be configured at the destination. For CNAME, enter only a hostname without https:// or a path; A records use a public IPv4; Redirect uses a complete URL.

Vercel

This is the tested Vercel flow for a subdomain already claimed at AICLUB.

1. Create and deploy the Vercel project

In Vercel, select New Project. Upload with Vercel Drop or connect your repository, choose a project name, then select Deploy.

Vercel New Project screen with Vercel Drop files and Deploy button.
Example: create a Vercel project from uploaded website files.

2. Confirm the production deployment succeeded

Wait until Vercel shows Congratulations or Ready, then select Continue to Project.

Vercel Congratulations screen after a successful deployment.
The project must deploy successfully before adding the custom subdomain.

3. Open Domains for the project

On the project Overview, select the + beside Domains or open Domains from the project navigation. You can also use Add Custom Domain from the checklist.

Vercel project Overview showing the Domains control and Add Custom Domain option.
Open the project domain settings after the production deployment is ready.

4. Add your AICLUB subdomain

Enter the exact subdomain you claimed at AICLUB, for example yourname.aiclub.ai.id. Keep Production selected, then choose Add Domain.

Vercel Add Domains dialog with a claimed AICLUB subdomain entered for Production.
Use the exact claimed hostname, not the Vercel project hostname.

5. Copy Vercel's required CNAME value

Vercel may first show Invalid Configuration. In DNS Records, copy the complete value shown in the CNAME row. This value is unique to the domain verification request.

Vercel DNS Records showing the CNAME value required to verify a custom subdomain.
Copy the CNAME Value exactly as Vercel displays it.

6. Save the CNAME in AICLUB and verify

In the matching AICLUB claim, choose CNAME, paste the Vercel value as the Target, and save. Do not add https://, a slash, or a path. Wait for DNS to update, then return to Vercel and select Refresh if needed. The setup is ready when Vercel shows Valid Configuration.

Vercel domain row showing Valid Configuration for a custom subdomain.
Final state: Vercel confirms Valid Configuration for the production domain.

Netlify
  1. Open your Netlify site → Site settings → Domain management.
  2. Add yourname.aiclub.ai.id as a custom domain.
  3. For external DNS, use the site hostname such as site-name.netlify.app as the CNAME target in AICLUB; no scheme or path.
  4. After DNS ACTIVE, return to Netlify and complete verification.
  5. Netlify issues SSL automatically after the domain points correctly.

Cloudflare Pages
  1. Open your Pages project → Custom domains → Set up a custom domain.
  2. Add yourname.aiclub.ai.id.
  3. Use the project hostname such as project.pages.dev as the CNAME target in AICLUB; no scheme or path.
  4. Keep the platform CNAME DNS-only; do not enable Cloudflare proxy for this record.
  5. If a zone/account warning appears, continue CNAME verification without moving nameservers. Wait for the custom domain and SSL to become active.

GitHub Pages
  1. Open the repository → Settings → Pages.
  2. Make sure the site is published, then enter yourname.aiclub.ai.id under Custom domain and Save.
  3. The AICLUB CNAME target must be the bare default hostname such as username.github.io; never append /repository-name or https://.
  4. Wait for the DNS check to show success.
  5. Required: enable Enforce HTTPS. Setup is not complete until it is checked.
  6. Use GitHub TXT domain verification when available so another party cannot take the domain.
  7. If Enforce HTTPS is unavailable, wait for domain and certificate verification before sharing the URL.
GitHub Pages settings with a verified custom domain and Enforce HTTPS enabled.
Example: the custom domain is verified and Enforce HTTPS is enabled.

VPS or your own server
  1. Use an A record with the public IPv4 only; do not enter a URL, port, or path.
  2. Allow TCP ports 80 and 443 through the firewall/security group and router.
  3. Configure a virtual host/server_name for yourname.aiclub.ai.id.
  4. For a static site on Caddy, use root * /var/www and file_server; for an app, use reverse_proxy 127.0.0.1:4000.
  5. Issue TLS and test from outside the server. Caddy can automate HTTPS after DNS and ports are ready; Nginx commonly uses ACME/Certbot.

Sources and review date

Last reviewed: 2026-10-25. Primary setup documentation: Cloudflare Pages, Vercel, Netlify, and GitHub Pages. Terakhir ditinjau: 2026-10-25; sumber utama adalah dokumentasi resmi penyedia di atas.