Connect a custom domain

You can use your own domain with any webgrow24 app. We do not charge for pointing. We issue a free Let's Encrypt SSL certificate that renews automatically. The whole flow takes under an hour for most domains.

What you need

• A domain you already own (any registrar — GoDaddy, Namecheap,

BigRock, Hostinger, etc.).

• An active webgrow24 app with a working default URL.
• Access to your registrar's DNS panel.

Step 1 — Add the domain to your app

Open the app in the dashboard. Click Domains in the side nav. Click Add domain and type the full domain — blog.example.in, not just example.in. If you want both example.in and www.example.in to work, add both.

The app detail screen now shows the records you need to add at your registrar.

Step 2 — Add the DNS records at your registrar

Two records:

For blog.example.in (and any other subdomain)

| Type | Host | Value | |---|---|---| | CNAME | blog | <your-app>-palak-ravi.webgrow24.in. |

For example.in (the apex / naked domain)

| Type | Host | Value | |---|---|---| | A | @ | 192.168.24.51 (replace with the current load-balancer IP shown in the dashboard) |

If your registrar does not allow a CNAME on the apex (some do not), you need an ALIAS or ANAME record instead. Most modern registrars support this.

Step 3 — Wait for DNS propagation

DNS changes take 5 minutes to 48 hours to propagate, depending on the TTL you set and the registrar. You can check propagation from your terminal:

``bash dig +short blog.example.in CNAME ``

When the answer is <your-app>-palak-ravi.webgrow24.in., the DNS is live.

Step 4 — Turn on SSL

The moment DNS resolves, our system requests a Let's Encrypt certificate for your domain. You will see the SSL status flip from Pending to Active in the dashboard within five minutes. The certificate renews itself 30 days before expiry. You do nothing.

Step 5 — Set the primary domain

If you added both example.in and www.example.in, pick the one you want customers to see. Open Domains in the app, click the row you want to be primary, and click Set primary. The other domain will 301-redirect to it.

Common issues

"DNS not propagating"

Your registrar might cache old records. Try lowering the TTL on the old A record to 300 seconds (5 minutes) before you change it. Also try clearing your local DNS cache:

``bash # macOS sudo dscacheutil -flushcache # Windows ipconfig /flushdns # Linux (systemd-resolved) sudo resolvectl flush-caches ``

"SSL stuck on Pending"

Almost always means the DNS does not yet resolve to our load balancer. Wait for the dig check above to succeed, then check back.

"I have a CAA record blocking Let's Encrypt"

A CAA record tells CAs which issuers are allowed to issue for your domain. If you have one, add letsencrypt.org to the allowed issuers.

"I bought the domain yesterday"

Some registrars lock new domains for 24–48 hours before allowing DNS changes. This is ICANN policy and we cannot work around it.

What we do not do (yet)

We do not sell domain registration in v1. We do not transfer domains between registrars. Bring-your-own-domain is the only supported flow. Domain registration is on the v2 roadmap.

If you have a domain that will not cooperate after following this guide once, open a support ticket. Our team responds in under an hour during business hours IST, and within four hours otherwise.