Subdomains & Custom Domains

Every store on Lokzon comes with a free subdomain at <your-slug>.lokzon.com. This is the address your customers use to reach your store. The subdomain is set when you first create your store, and you can change it later if you need to — though changing it means customers who knew your old URL will have to use the new one.

If you want a more professional address using your own brand (like shop.yourbrand.com or www.yourbrand.com), you can connect a custom domain to your store as well.

---

Part 1: Your Free Subdomain

1.1 What You Get

When you create your store, Lokzon automatically assigns you a subdomain such as my-store.lokzon.com. Customers visit this URL to browse your storefront. The subdomain cannot be removed — it stays with your store for as long as it exists.

1.2 Where to Find It

Go to /dashboard/shop and select the Domain tab. The first card on this page is Store name & public URL. It shows your current subdomain and store name.

1.3 Changing Your Subdomain

If you ever need to change your subdomain — for example, you picked the wrong name during onboarding — you can do so from the Store name & public URL card.

A note before you change it: Your old URL will stop working as soon as you save. Any links, bookmarks, marketing materials, or business cards with the old URL will need to be updated. Most stores keep their original subdomain for the lifetime of the business.

To change it:

1. Open the Store name & public URL card under /dashboard/shop → Domain.
2. Type the new slug you want in the Public store URL field. The slug is the part before .lokzon.com.
3. As you type, the system checks whether the slug is available:
   • A green message confirms it is available.
   • A red message tells you it is already taken.
   • If it is taken, the system shows up to four suggested alternatives (for example, my-store-2, my-store-3).
4. Click Save store name & URL.

Only the store owner can change the subdomain. Other team members see the current URL but cannot edit it.

1.4 Important Note Before Changing

Before you save a new subdomain, keep in mind:

• Your previous subdomain URL stops working immediately.
• Any links you shared (social media, business cards, ads, search results) will break.
• Customers who bookmarked your old URL will see an error unless they find you through the new one.
• Changing the subdomain does not affect any custom domain you may have connected.

1.5 Subdomain Rules

When picking a subdomain, follow these rules:

• Use lowercase letters, numbers, and single hyphens only.
• The slug must be at least 3 characters long.
• Some words are reserved by the system and cannot be used. Reserved names include admin, api, preview, dashboard, lokzon, system, auth, login, signup, www, mail, blog, support, help, billing, account, settings, manage, app, dev, staging, prod, test, root, localhost, status, portal, assets, static, media, images, and cdn.

1.6 Tips for Picking a Good Slug

• Keep it short and easy to remember.
• Match it to your brand name when possible.
• Avoid numbers if you can — they are harder to share verbally.
• If your first choice is taken, add a city or category, like karim-fashion-dhaka.

---

Part 2: Connecting a Custom Domain

A custom domain is a domain you bought from a registrar (such as GoDaddy, Namecheap, Cloudflare, or any local provider like DianaHost, ExonHost, EIC, Dhaka Web Host) that points directly to your Lokzon store. You can use either a root domain (yourbrand.com) or a subdomain (shop.yourbrand.com).

2.1 Before You Start

Make sure you have:

• A domain you own, purchased from any DNS registrar.
• Access to your registrar's DNS management panel.
• About 10 to 20 minutes for DNS records to propagate (local Bangladeshi providers may take up to 24 hours).

2.2 Where to Manage It

Go to /dashboard/shop → Domain tab. Scroll down to the Custom domain card. Only the store owner can manage the custom domain.

The card has three states:

• No domain added — you see an input field and a Start verification button.
• Verification in progress — you see the DNS records you need to add, the status of automatic checks, and a Verify now button.
• Verified — your custom domain is active with automatic SSL, and a Remove custom domain button is shown.

2.3 Step 1: Enter Your Domain

1. In the Custom Domain card, type the domain you want to use. Examples:
   • shop.yourbrand.com (a subdomain)
   • yourbrand.com (your root domain)
   • www.yourbrand.com (the www version of your root domain)
2. Click Start verification.

The system prepares the records you need and shows them on the page.

2.4 Step 2: Add DNS Records at Your Registrar

After clicking Start verification, the page shows two DNS records. Open your registrar's DNS management panel (often called "DNS Settings", "DNS Management", or "Zone Editor") and add these two records:

CNAME Record — used to point your domain at Lokzon's servers.

• Type: CNAME
• Name/Host:
  • If you are using a subdomain like shop.yourbrand.com, enter the part before your domain — for example, shop.
  • If you are using a root domain like yourbrand.com, enter @ (or leave it blank, depending on your registrar).
• Value/Target: Copy the value shown on the page (it looks like <random-string>.lokzon.com). Use the copy button next to the input.
• TTL: Auto, 300, or 14400 is fine.

TXT Record — used to prove that you own the domain.

• Type: TXT
• Name/Host: _lokzon-verify
• Value/Target: Copy the random token shown on the page.
• TTL: Auto or 3600.

2.5 Step 3: Verification & Automatic Background Polling

After saving both records at your registrar:

• Automatic Background Verification: You do not need to click "Verify now" repeatedly. Lokzon's automated background system periodically checks your DNS records every few minutes. Once your DNS propagates, your domain will link automatically.
• Manual Verification: You can also click Verify now at any time to run an instant check.

The system checks both records:

• If the CNAME points to the correct target and the TXT record contains the correct token, your custom domain becomes Verified. Customers can now reach your store through it with automatic SSL.
• If either record is missing or incorrect, the page tells you which one failed:
  • "CNAME verified: No" — your CNAME record is wrong or not yet propagated.
  • "TXT verified: No" — your TXT record is wrong or not yet propagated.

You can click Verify now again after fixing the records.

2.6 Registrar-Specific Rules, Gotchas & Workarounds

Different domain registrars and DNS hosts handle records differently. Find your provider below for exact steps, critical rules, and workarounds. If yours isn't listed, use the Other / Standard Registrar guidance at the end.

1. cPanel & Local Bangladeshi Registrars (DianaHost, ExonHost, EIC, Dhaka Web Host, etc.)

• The Gotcha: cPanel automatically appends your domain name to whatever you type in the "Name/Host" field.
• The Correct Rule: In the TXT Record Name field, type ONLY _lokzon-verify (or _lokzon-verify.<subdomain> if setting up a subdomain). Do NOT type _lokzon-verify.yourdomain.com, otherwise cPanel will save it as _lokzon-verify.yourdomain.com.yourdomain.com, causing verification to fail.
• Where to go: cPanel → Zone Editor (under the Domains section) → select your domain.
• Steps: Click + Add Record, choose CNAME, enter Name = <your host> and CNAME Value = <the value shown in Lokzon>. Then add a second record, choose TXT, enter Name = _lokzon-verify (only that) and Value = <the token shown in Lokzon>. Set TTL to 14400 or 300 and save.

2. Hostinger (hPanel)

• Where to go: Log in to hPanel → Domains → click your domain → Manage → in the left sidebar open DNS / Nameservers → scroll to Manage DNS Records.
• Steps:
  1. Click Add record. Set Type = CNAME, Name/Host = <your host> (e.g. @, www, or shop), Target/Content = the CNAME value shown in Lokzon, TTL = 300 (or leave default). Click Add record.
  2. Add a second record. Set Type = TXT, Name/Host = _lokzon-verify, Content = the verification token shown in Lokzon, TTL = 300. Click Add record.
• Note: Hostinger requires the DNS / Nameservers section to be on Lokzon's recommended / default nameservers for the records you add here to take effect. If your domain uses external nameservers (for example, Cloudflare), manage the records there instead.

3. Plesk

• Where to go: Plesk Domains → your domain → DNS Settings (sometimes under Hosting & DNS).
• The Gotcha: Like cPanel, Plesk may auto-append the domain in the record name. When adding a TXT record, enter only _lokzon-verify as the record name.
• Steps: Click Add Record, pick CNAME, set the record name and the CNAME value from Lokzon, save. Add another record, pick TXT, set name _lokzon-verify and the token value, save.

4. DirectAdmin

• Where to go: DirectAdmin Domain Setup (or DNS Management) → select your domain.
• Steps: Click Add Record. Choose CNAME — Name = <your host>, Value = the CNAME value from Lokzon. Then choose TXT — Name = _lokzon-verify, Value = the token. TTL can stay at 14400. Save.

5. Cloudflare DNS

• The Gotcha: Cloudflare's orange-cloud Proxy masks CNAME targets behind Cloudflare's IP addresses, so verification fails while proxied.
• The Correct Rule: When adding the CNAME record, set Proxy status to DNS only (grey cloud) during verification. You may turn on Proxying (orange cloud) after the domain shows Verified in Lokzon.
• Where to go: Select the domain → DNS → Records → Add record.
• Steps: Type = CNAME, Name = <your host>, Target = the CNAME value from Lokzon, Proxy status = DNS only. Then Type = TXT, Name = _lokzon-verify, Content = the token. Save both.

6. GoDaddy

• Where to go: GoDaddy My Products → Domains → select your domain → Manage DNS (in the DNS section, or DNS records).
• Steps:
  1. Under Records, click Add New Record. Type = CNAME, Host = <your host> (e.g. www or shop; for a root domain GoDaddy may not allow @ — see the root-domain workaround below), Points to = the CNAME value from Lokzon, TTL = 1 hour. Save.
  2. Add a second record. Type = TXT, Host = _lokzon-verify, Value = the token, TTL = 1 hour. Save.
• Note: GoDaddy appends the domain to the Host field automatically — enter only the subdomain prefix (e.g. www, shop) or the underscore prefix (_lokzon-verify), never the full domain.

7. Namecheap

• Where to go: Namecheap Domain List → select your domain → Manage → Advanced DNS.
• Steps:
  1. Under Host Records, click Add New Record. Type = CNAME Record, Host = <your host> (e.g. www; Namecheap's default @ CNAME may be locked — see root-domain workaround below), Value = the CNAME value from Lokzon, TTL = Automatic. Click the green checkmark to save.
  2. Add another record. Type = TXT Record, Host = _lokzon-verify, Value = the token, TTL = Automatic. Save.
• Note: Namecheap shows a green check to save and a red X to discard — always confirm with the checkmark.

8. Wix

• Where to go: Wix Dashboard → Settings → Domains → Connect a Domain (for a domain already connected) → Manage → DNS Records (or Advanced → DNS Records).
• The Gotcha: Wix puts your site on A records and its own proxying. Adding a CNAME to the same host can conflict.
• Steps: In the DNS Records manager, add the CNAME (Host = <your host>, Value = CNAME value from Lokzon) and the TXT (_lokzon-verify = token). If Wix has an existing A record on the same host, leave the CNAME host to a subdomain such as www or shop, or remove the conflicting A record if it is not needed.
• Note: If your Wix site also needs to keep serving, verify with a subdomain (shop.yourdomain.com) instead of the root so you don't take the whole domain off Wix.

9. Squarespace Domains (incl. former Google Domains)

• Where to go: Squarespace Dashboard → Settings → Domains → select your domain → DNS (or Advanced Settings).
• The Gotcha: Squarespace hides some records behind an "Advanced" section, and it manages a default CNAME for its own site.
• Steps: In DNS → scroll to CNAME Records, click Add, set Host = <your host>, and paste the CNAME value from Lokzon. Then in TXT Records, click Add, Host = _lokzon-verify, paste the token. Save.

10. WordPress.com

• Where to go: WordPress.com Upgrades → Domains → select your domain → DNS Records.
• The Gotcha: WordPress.com (especially free/WP.com-hosted plans) may not allow adding a custom CNAME/TXT directly; you can add them under DNS Records on the domain's management page, but on some plans only the root A records are editable.
• Workaround: If you cannot add a TXT/CNAME there, move the domain's DNS to a provider that allows full record control (e.g. Cloudflare Free) by pointing the domain's nameservers there, then add the records in that provider.

11. Cloud DNS & VPS Panels (AWS Route 53, Google Cloud DNS, Azure DNS, Vultr, DigitalOcean)

• Where to go: Open the domain's Hosted Zone / DNS page in the cloud console.
• Steps: Create a CNAME record set with Name = <your host> (e.g. www, shop) and Value = the CNAME value from Lokzon. Create a TXT record set with Name = _lokzon-verify and Value = the token. Leave TTL at the default (or 300). Save.

12. Root Domains (yourdomain.com without www) & CNAME Flattening Restrictions

• The Issue: Standard DNS RFC specifications forbid CNAME records directly on the root/apex domain (@), and many providers do not support CNAME flattening (ALIAS/ANAME records).
• The Workaround:
  1. Add www.yourdomain.com as your custom domain in Lokzon and configure www as the CNAME host.
  2. In your registrar control panel, set up a free URL Forwarding / Domain Redirect from yourdomain.com → https://www.yourdomain.com (301 Permanent Redirect).
• Providers that allow @ CNAME: Cloudflare (with CNAME flattening enabled), some premium DNS hosts. For everyone else, the www + redirect approach is the reliable path.

13. Cleaning Stale / Legacy DNS Records

• The Issue: Lingering A or CNAME records from previous hosting platforms (Shopify, Wix, WordPress, Squarespace, or old cPanel servers) cause routing conflicts.
• The Workaround: Delete all old A records (such as Shopify's 23.227.38.65 or old server IPs) and old CNAME records pointing to former hosts before verifying. Keep unrelated records (MX, SPF/TXT for email) untouched.

14. Standard Registrar (Not Listed Above)

• Where to go: Log in to your domain provider → open DNS Management / Zone Editor / Advanced DNS.
• Steps: Add a CNAME record: Name = <your host>, Value/Target = the CNAME value from Lokzon. Add a TXT record: Name = _lokzon-verify, Value = the token shown in Lokzon. Save both and wait 10–20 minutes.

Common Edge Cases (Applies to All Providers)

• Record Name auto-append: Many panels (cPanel, Plesk, GoDaddy, Namecheap) automatically append your domain to the Name/Host field. Enter only the prefix (www, shop, _lokzon-verify) — never the full domain.
• Trailing dot: Some providers accept the CNAME value with or without a trailing dot (e.g. <value>.lokzon.com.). Both are fine.
• TXT quotes: If a panel wraps the TXT value in quotes automatically, keep them; the value inside must still match exactly. Do not add extra spaces.
• TTL doesn't need to be exact: Auto, 300, 3600, or 14400 all work.
• Extra spaces break verification: Copy the values with the copy button in Lokzon to avoid invisible spaces.
• DNS-only vs proxying: If your provider offers CDN/proxying (Cloudflare, some others), verify with DNS only first.
• Email records: Don't delete existing MX or SPF (TXT) records — they are needed for email and do not conflict with your domain verification.

2.7 Propagation Timelines & Local ISP Delay

DNS changes do not happen instantly worldwide:

• Global Providers (Cloudflare, Namecheap, GoDaddy): Usually propagate in 10 to 20 minutes.
• Local Bangladeshi Providers (DianaHost, ExonHost, etc.) & Local ISPs: DNS cache update on local ISPs (Grameenphone, Robi, Banglalink, AmberIT, BTCL) can take up to 24 hours. Please allow adequate time before retrying.

2.8 What if Verification Fails?

If your records are correct but verification fails:

1. Double-check for extra spaces in the CNAME or TXT target values.
2. Verify you used CNAME and TXT record types (not A or AAAA).
3. Check cPanel double-domain append issues (_lokzon-verify vs _lokzon-verify.domain.com).
4. Check Cloudflare Grey Cloud setting (DNS Only).
5. Wait 20 minutes for local DNS caches to clear.

2.9 Verification Expiry

You have 72 hours from the moment you click Start verification to complete the DNS setup. If 72 hours pass before verification completes, the request expires. To start over, click Cancel & Retry or Start verification again to get a fresh CNAME target and TXT token.

2.10 Removing a Custom Domain

If you ever want to remove your custom domain:

1. Open the Custom domain card under /dashboard/shop → Domain.
2. Click Remove custom domain.
3. Confirm the removal in the dialog.

After removal, customers will no longer reach your store through the custom domain — they will use your free <your-slug>.lokzon.com address instead.

---

Part 3: Common Questions

3.1 Can I use a subdomain like www.yourbrand.com?

Yes. The setup works the same way. Enter www.yourbrand.com as the custom domain and use www as the CNAME Name/Host.

3.2 Do I need to click "Verify now" repeatedly?

No. Lokzon automatically checks your DNS records in the background every few minutes. Once your DNS propagates, your store will connect automatically.

3.3 What if my registrar doesn't allow a CNAME on @?

Use www.yourbrand.com as your primary domain in Lokzon, and set up a free 301 URL Redirect from yourbrand.com to https://www.yourbrand.com at your registrar.

3.4 Why does cPanel verification fail when I enter _lokzon-verify.mybrand.com?

cPanel automatically appends .mybrand.com. Enter ONLY _lokzon-verify in the Name field to avoid creating a double domain.

3.5 Why does Cloudflare verification fail?

Ensure the Proxy Status toggle on your CNAME record is set to DNS Only (Grey Cloud). Orange Cloud hides your CNAME target IP and blocks verification.

3.5b My provider isn't listed — what do I do?

Almost every registrar exposes a DNS manager under a name like "DNS Management", "Zone Editor", "Advanced DNS", or "Manage DNS Records". Open it, then add a CNAME record (Name = your subdomain prefix or www, Value = the CNAME value shown in Lokzon) and a TXT record (Name = _lokzon-verify, Value = the token shown in Lokzon). Save both and wait 10–20 minutes.

3.5c My domain's DNS is hosted somewhere other than where I bought it (e.g. nameservers point to Cloudflare)

DNS records are managed wherever your domain's nameservers point, not where you bought the domain. Log in to that DNS host (e.g. Cloudflare) and add the records there. If your nameservers point at your web host (cPanel/Plesk), add them in the host's panel instead.

3.5d Can I keep my existing website/email while adding the domain?

Yes. Only the CNAME and TXT records you add for Lokzon are used. Existing MX (email) and SPF records are untouched. If your root domain currently hosts a website (Wix, WordPress, a landing page), prefer connecting a subdomain such as shop.yourdomain.com so the root site keeps working.

3.6 Can I connect two different domains to the same store?

No. Each store can have only one custom domain attached at a time. If you want to switch, remove the current custom domain first, then add the new one.

3.7 Can I keep my custom domain even if I change my subdomain?

Yes. The free subdomain (<slug>.lokzon.com) and your custom domain are independent. Changing one does not affect the other.

3.8 What happens to my custom domain if I downgrade my plan?

Your custom domain stays attached as long as your store is active. If your store is suspended or deleted, the custom domain attachment is removed.

3.9 Does this affect my subdomain?

No. Both work at the same time. Customers can reach your store using either URL.

3.10 Can I use my custom domain for email too?

This guide covers only the storefront. To set up email on your custom domain (for example, hello@yourbrand.com), use your registrar's email service or a third-party email provider — it is separate from Lokzon.

---

Part 4: Quick Reference

Where to Find Things

DNS Records You Add

Registrar Specific Quick Cheat-Sheet

Common Edge Cases

Time Limits & Propagation

---

End of Guide

Your store now has a strong web address — either a free <your-slug>.lokzon.com subdomain or your own branded domain. Both options give customers a clean, professional way to find your store.