Blog
Technical6 min read

Custom Domains: The Complete Setup Guide for Web Agencies

Connecting a client's domain to their AiBuildPro website takes under 5 minutes — once you know what you're doing. Here's the exact process, common pitfalls, and how to explain it to clients.

A

AiBuildPro Team

7 April 2026

🌐

Every professional website delivery ends with the same milestone: the client's domain going live. It's the moment that makes the project feel real. But DNS configuration trips up even experienced developers — especially when different registrars have different interfaces, and propagation times are unpredictable.

This guide covers everything you need to know to confidently connect any domain to an AiBuildPro website.

What happens before you touch DNS

Before you configure DNS, make sure:

  1. The website is generated and published in AiBuildPro (it should be live at slug.aibuildpro.in)
  2. Your client has access to their domain registrar, or you have the login credentials
  3. You know what subdomain to use — www.client.com only, root domain only, or both

Most clients want both www and the root domain (client.com) to work. We'll cover both.

Step 1: Add the domain in AiBuildPro

Go to the website detail page and click Add Custom Domain. Enter the domain — just the domain name itself, without https:// or trailing slashes. For example: rahultailors.com or www.rahultailors.com.

If your client wants both www and the root to work, add www.rahultailors.com as the primary domain. AiBuildPro will handle routing the root to www automatically.

Step 2: Add DNS records at the registrar

This is where most agencies spend the most time — every registrar's interface looks different, but the records you need are the same:

For the www subdomain (or any subdomain like shop.client.com):

  • Type: CNAME
  • Name/Host: www (or the subdomain)
  • Value/Points to: sites.aibuildpro.in
  • TTL: 3600 (or "Automatic")

For the root domain (@ or the bare domain):

  • Type: A
  • Name/Host: @ (some registrars show this as blank or the domain name itself)
  • Value/IP: 76.76.21.21
  • TTL: 3600
Why can't you use a CNAME for the root domain? The DNS spec doesn't allow CNAME records at the zone apex (root domain) because it would conflict with MX, SOA, and NS records. Some modern registrars offer "CNAME flattening" (GoDaddy calls it "ALIAS") — if available, use that instead of the A record.

Step 3: Wait for propagation

After saving the DNS records, click Verify Domain in AiBuildPro. The check runs immediately — but DNS changes take time to propagate. In practice:

  • Most registrars push changes within 5–30 minutes
  • Full global propagation can take up to 48 hours
  • Your local ISP may cache the old record for longer than the TTL

Use whatsmydns.net to check propagation status from multiple global locations — this helps distinguish between "not propagated yet" and "misconfigured."

Step 4: SSL is automatic

Once the domain is verified, AiBuildPro provisions a free SSL certificate via Let's Encrypt automatically. This usually takes 1–2 minutes after successful verification. The site becomes accessible at https:// without any configuration on your part.

You don't need to buy an SSL certificate. You don't need to configure anything. It just works.

Common problems and fixes

"Verify Domain" keeps showing pending after 2+ hours: Double-check the CNAME value — a common mistake is using the full URL (https://sites.aibuildpro.in) instead of just the hostname (sites.aibuildpro.in). Also check there are no trailing spaces.

www works but root doesn't (or vice versa): You need both an A record for the root AND a CNAME for www. Adding only one won't cover both. Verify in whatsmydns.net which record is propagated and which isn't.

Client's old website shows instead of the new one: The old site is probably still pointed to a different server. You've added the new records, but there might also be an old A record pointing elsewhere. Delete the conflicting records at the registrar.

Mixed content warnings (some resources load over HTTP): Regenerate and republish the website from the AiBuildPro dashboard. This ensures all internal links use the new domain with HTTPS.

How to explain DNS to clients

Clients often don't understand why "it's not live yet" when you've "already configured it." A useful analogy:

"DNS is like a phone book. We've updated your entry in the phone book, but the old book still exists in many places around the world. Over the next few hours, phone books everywhere will update with your new address. Until then, some people will still be directed to the old site."

Setting this expectation upfront — "it will be live within 24 hours, usually much sooner" — prevents the post-delivery anxiety call.

#domains#dns#ssl#hosting

Ready to try AiBuildPro?

Build your first client website in under 5 minutes. Free 7-day trial, no credit card required.