Your Elbuz CMS store opens on your own domain, not the temporary elbuz.shop address. Add one CNAME record to the domain's DNS; the service issues the HTTPS certificate itself.
When you need this:
- Domain bought, store on elbuz.shop — one CNAME record, and shoppers see your address.
- You need HTTPS — the certificate is issued in 5–10 minutes and renews itself.
- Old site on this domain — switch with one record; the temporary address keeps working.
- Domain already in Cloudflare — replace the A record with a CNAME.
Where to start: add www → CNAME → shops.elbuz.shop to DNS, then click “Connect your domain” in the “Elbuz CMS” template.
What domain connection does
- Opens the store on your domain — one CNAME record and one button in the template.
- Issues HTTPS without your involvement — the certificate appears on its own; no
_acme-challengerecords needed. - Shows the domain status — the “Own domain” line shows whether the record was found and whether the certificate is ready.
- Works with a domain without www — via a CNAME on the root or a redirect to www.
- Gets along with your Cloudflare — the domain stays in your Cloudflare account.
What kind of domain you have
This determines which record to add. The store connects to one address: either www.example.com or example.com.
- Address with www or a subdomainwww.example.com, shop.example.com — a CNAME works with any provider. Recommended.
- Address without wwwexample.com — not every provider supports a CNAME on the root
- Domain DNS in CloudflareYour own Cloudflare account, or the domain was bought from Cloudflare Registrar
How to connect a domain: three steps
- Add a CNAME record in the domain's control panel (at the registrar or wherever its DNS records are managed):
Delete any old-hosting A or AAAA records forField What to enter Type CNAMEName (Host, Subdomain) www— the subdomain only, without your domainValue (Target, Points to) shops.elbuz.shopTTL any, for example 300 or “Auto” www: they don't work alongside a CNAME. - Enter the domain in the template. Open the “Elbuz CMS” template: in the “Store” section, under the store address, click “Connect your domain”. Enter the address, for example
www.example.com, and confirm. The program checks that the domain already points to the store and connects it. - Wait for HTTPS. The status is in the “Own domain” line of the “Store” section (“not connected” until you enter a domain). While the certificate is issued, it reads “waiting for the CNAME record … and the HTTPS certificate”, usually for 5–10 minutes. With the template open, the line refreshes every minute. Once it reads “Domain … is connected, HTTPS works”, the store opens on your address.
1
Own domain status2
Connect your domain3
Address- Domain status: not connected, waiting for the CNAME record and certificate, or connected with HTTPS working.
- Opens the window where you enter your domain.
- The address the store is open at right now.
1
CNAME value2
Domain address field- This value goes into the CNAME record in your domain control panel.
- Enter the domain address here, for example www.example.com.
After connection, all “Elbuz CMS” templates get the new address, including order import, and the “Site address” field shows your domain. Exports work right away without waiting for the certificate. The temporary address on elbuz.shop keeps working.
Connecting a domain launches the store, just like “Launch store”: the trial ends, the “Trial store” block disappears, and the store runs with no time limit while the account is paid and exports keep coming. A store suspended for the trial or 60 days without exports is turned on first, then the domain connects. A suspension due to a disabled account stays: the store turns on by itself after payment. While suspended, your domain and the temporary address show the “Store temporarily suspended” page. More: trial store and launch.
Don't enter the full domain in the name field. Most panels append the domain to the name themselves, so www.example.com turns into www.example.com.example.com. The name field takes only www.
If the domain has CAA records, they must allow the certificate authorities letsencrypt.org, pki.goog, ssl.com and digicert.com. No CAA records — nothing to do.
Domain without www
Under the DNS standard, the root domain (example.com, shown as @ in panels) can't have a CNAME record. Some providers work around this with an ALIAS, ANAME or “CNAME flattening” record: Cloudflare, Porkbun and others. Whether yours does — see the provider table.
| Your provider | What to do |
|---|---|
| Supports CNAME, ALIAS or ANAME on the root | Add such a record for @ pointing to shops.elbuz.shop and connect example.com in the template. |
| Doesn't support it | Connect the store on www.example.com (CNAME, as in the three steps) and redirect the root to https://www.example.com using the registrar's domain forwarding service. |
The store connects to one address. So for the pair example.com + www.example.com, one becomes the store address and the other redirects to it. The www option works with every provider.
Domain already in Cloudflare
If the domain's DNS is managed by Cloudflare — your account, or the domain was bought from Cloudflare Registrar — the domain stays there. There's nothing to transfer.
- Cloudflare → your domain → DNS → Records.
- Find the old hosting's A (or AAAA) record for the name you need and delete it or change its type to CNAME.
- Name —
wwwor@, Target —shops.elbuz.shop. The root works in Cloudflare: it converts a CNAME on@by itself (CNAME flattening). - Proxy status — DNS only (grey cloud). Save.
Why the grey cloud: the store already runs through Cloudflare on our side — with protection, caching and HTTPS. The orange cloud (Proxied) layers your own rules on top: “Cache Everything” can cache shoppers' personal pages, and the “Flexible” SSL mode and WAF rules will apply too. You don't need to turn off anything else in Cloudflare.
Where to add a CNAME with your provider
You add the record wherever the domain's DNS records are managed. Usually that's the registrar, but if the domain is “parked” on a hosting account, it's the hosting panel. Section names were checked against provider help pages in October 2026; interfaces change, so look for the words “DNS”, “records”, “zone”.
| Provider | CNAME for www | Root without www | Root redirect to www |
|---|---|---|---|
| Imena.ua | yes | — | Web редирект (301) |
| NIC.UA | yes, with a trailing dot | — | Permanent Redirect (http only) |
| ukraine.com.ua | yes | ALIAS | ALIAS is better (the redirect also affects www) |
| Hostiq, HostPro (cPanel) | yes | — | — |
| Mirohost | yes | — | — |
| Hostinger | yes | ALIAS (type CNAME, name @) | Forward domain |
| Cloudflare | yes | CNAME (flattening) | not needed |
| GoDaddy | yes | no | Forwarding (301) |
| Namecheap | yes | ALIAS Record | URL Redirect Record (301) |
| AWS Route 53 | yes | no | none built in |
| Squarespace Domains | yes | ALIAS (without DNSSEC) | Domain Forwarding |
| Porkbun | yes | ALIAS - CNAME flattening | URL Forwarding |
| OVHcloud | yes, with a trailing dot | no | Redirection (http only) |
| Hetzner | yes | no | none |
“—” means the provider's help pages don't cover it: ask their support. An “http only” redirect won't work for a shopper who types https://example.com. If you need the root and your provider doesn't support it, move the domain's DNS to free Cloudflare and follow the “Domain already in Cloudflare” section.
Imena.ua
Control panel → domain name → “Налаштування домену (DNS та редиректи)” (domain settings) → “Перейти до налаштування домену” (opens dnshosting.org) → “Додати запис” (add record). Host — www, type — CNAME, data — shops.elbuz.shop. Root redirect: “Web редирект”, type “Прямий редирект (301-й)” (direct 301). Changes apply within 24 hours.
NIC.UA
The domain must use NIC.UA name servers. “Name Servers (NS)” → gear next to the domain's NS → “Змінити” (change) next to DNS records. Name — www, type — CNAME, value — shops.elbuz.shop. with a trailing dot, or NIC.UA appends your domain. Root redirect: an @ record of type “Permanent Redirect” to https://www.example.com, http only.
ukraine.com.ua (Hosting Ukraine)
adm.tools → “Налаштування домену (DNS)” (domain DNS settings) → “Додати запис” (add record). Subdomain — www (no domain name), type — CNAME, data — shops.elbuz.shop. The root supports ALIAS: subdomain empty or @, type ALIAS, data — shops.elbuz.shop. Its “Веб-редирект” (web redirect) also redirects www, so for www + root use ALIAS.
Hostiq, HostPro and other cPanel hosting
cPanel → “Domains” → “Zone Editor” → “Manage” next to the domain → “Add Record” (or “CNAME”). Name — www (cPanel appends the domain; a full name needs a trailing dot: www.example.com.), type — CNAME, record — shops.elbuz.shop. Hostiq without hosting: “Мои домены” → “Детали” → “NS серверы” → turn on DNS management → “Управление DNS” (My domains → Details → NS servers → DNS management).
Mirohost
The domain must use Mirohost name servers. Control panel → hosting service → domain → “Zone management” → “Zone settings”. Add a www record of type CNAME with the value shops.elbuz.shop and apply the changes.
Hostinger
hPanel → “Domains” → “Manage” → “DNS / Nameservers”. Type — CNAME, Name — www, Target — shops.elbuz.shop. For the root, choose type CNAME with Name @ — Hostinger saves it as an ALIAS. If Hostinger CDN is on, turn it off first: it takes the zone's only ALIAS.
GoDaddy
Domain Portfolio → domain → “DNS” → “Add New Record”. Type — CNAME, Name — www, Value — shops.elbuz.shop. GoDaddy doesn't allow a CNAME on the root (@). Redirect the root instead: “DNS” → “Forwarding” → “Add Forwarding” → https://www.example.com, type Permanent (301).
Namecheap
Domain List → “Manage” → “Advanced DNS” tab → “Add New Record”. Type — CNAME Record, Host — www, Value — shops.elbuz.shop → “Save All Changes”. For the root — ALIAS Record, Host @, Value shops.elbuz.shop; first delete other records on @ (A, AAAA, URL Redirect). Or a redirect: URL Redirect Record, Host @, Value https://www.example.com, Permanent (301).
AWS Route 53
Route 53 → “Hosted zones” → zone → “Create record”. Record name — www, Record type — CNAME, Value — shops.elbuz.shop, Routing policy — Simple routing. You can't connect the root here: Route 53 doesn't allow a CNAME on the root, and Alias only points to AWS resources. Connect the store on www.
Squarespace Domains (formerly Google Domains)
account.squarespace.com/domains → domain → “DNS” → “Custom Records” → “Add Record”. Type — CNAME, Name — www, Data — shops.elbuz.shop. For the root — Type ALIAS, Name @; first turn off DNSSEC (“DNS” → “DNSSEC”), because ALIAS doesn't work with it.
Porkbun
Domain Management → “Details” → “Edit” next to “DNS Records”. Type — CNAME, Host — www, Answer — shops.elbuz.shop. For the root — type “ALIAS - CNAME flattening” with an empty Host. If there's a CNAME record * (asterisk), delete it.
OVHcloud
Control Panel → “Web Cloud” → “Domain names” → domain → “DNS zone” tab → “Add an entry” → CNAME. Subdomain — www, Target — shops.elbuz.shop. with a trailing dot, or OVHcloud appends your domain. Root — redirect only: “Redirection” tab → “Add a redirection” → “To a web address” → “Permanent (301)”; it doesn't redirect https://.
Hetzner
DNS zones live in Hetzner Console. Project → “DNS” → zone → “Records”: type CNAME, name www, value shops.elbuz.shop → “Add record”. Hetzner has no ALIAS and no redirects — connect the store on www.
Other provider
Look for a “DNS”, “DNS records” or “Zone Editor” section in the panel. The rule is the same everywhere: type CNAME, name www, value shops.elbuz.shop. If after saving the check shows shops.elbuz.shop.example.com, add a dot at the end of the value.
How to check the record yourself
The easiest way is the “Own domain” line in the template's “Store” section. To check the record before connecting, open dnschecker.org, enter www.example.com and choose the CNAME type. Or use the Windows command prompt:
nslookup -type=CNAME www.example.com 1.1.1.1
The response should contain canonical name = shops.elbuz.shop. If you've just added the record and the check doesn't see it, wait: DNS servers remember a “no record” answer for up to 15–60 minutes.
Scenarios
A new domain with no site on it yet
Add a CNAME www → shops.elbuz.shop and redirect the root to https://www.example.com at the registrar. A few minutes later, click “Connect your domain”, enter www.example.com and wait for the “HTTPS works” line.
Moving from an old site to an Elbuz CMS store
Fill the store on the temporary address and check it. Then replace the old hosting's A records with a CNAME to shops.elbuz.shop and connect the domain in the template. HTTPS on your domain starts working a few minutes after the switch. Don't shut down the old hosting until you see the “HTTPS works” line.
A domain in Cloudflare with email and other records
Change only the site record (www or @) to a CNAME with the grey cloud. Leave MX, SPF, DKIM and other records alone: email will keep working as before.
What to do when the domain won't connect
| What you see | Why | What to do |
|---|---|---|
| “Domain … does not point to the store yet” | The CNAME record is missing, has a mistake, or DNS hasn't updated yet | Check the record (how to check), remove old A/AAAA records and try again in 15–60 minutes |
The check finds www.example.com.example.com |
The full domain was entered in the name field | Leave only www in the name (three steps) |
| “Domain … is already connected to another store” | This domain is linked to a store in another account | Write to support@elbuz.com |
| “Invalid domain name!” | The address contains spaces, underscores or Cyrillic characters | Enter a Cyrillic domain in punycode format (xn--…); your registrar shows it |
| “Could not connect domain …” | Cloudflare rejected the domain or the store server didn't respond | Try again in a few minutes; if it keeps happening, contact support |
| “Waiting for the CNAME record … and the HTTPS certificate” for more than an hour | Cloudflare doesn't see the CNAME: the record is wrong, an old A record sits next to it, or CAA blocks the certificate | Check the record and the CAA records |
| “Domain … is not confirmed” | The domain verification time ran out, or Cloudflare blocked it | Fix the record and click “Connect your domain” again |
FAQ
Do I need to transfer my domain to Elbuz?
No. The domain stays with your registrar, and DNS stays where it's managed now. You only add one CNAME record.
Will email on the domain stop working?
No, as long as you change only the site record (www or @). Leave the MX, SPF and DKIM records alone.
Do I need to buy an SSL certificate?
No. The certificate is issued automatically 5–10 minutes after the CNAME record appears and renews itself.
Who handles backups, updates and store protection?
The service. Backups, updates and the SSL certificate are our job, Cloudflare protection is on for all Elbuz CMS sites, and our own modules speed up the store. Your domain doesn't affect any of this.
Will the temporary address on elbuz.shop keep working?
Yes, it keeps working after you connect your own domain.
Do I need to click “Launch store” if I'm connecting my own domain?
No. Connecting your own domain launches the store by itself, and its trial ends. If the store was suspended because of the trial, the program turns it on first. More: connecting a domain launches the store.
Can I connect both example.com and www.example.com?
The store connects to one address. Redirect the other one to it at your registrar. More: domain without www.
How do I change the connected domain to another one?
Add the new domain's CNAME record, click “Connect your domain” and enter the new address. It replaces the old domain, which stops working at once: without the CNAME, the store is reachable only on the temporary address for a few minutes. HTTPS for the new domain appears in 5–10 minutes.
Where to find it and who has access
- Menu
- Directories → Operations → Data export → “Elbuz CMS” template → “Store” section
- Access right
- the export template card window in “Group permissions”
- Prepare
- a created store, access to the domain's control panel
The “Connect your domain” button appears once the store is created. You can't connect your own domain in the Elbuz demo version. How to create a store: “How to create an online store on Elbuz CMS”.
Related topics
- If you don't have a store yet — How to create an online store on Elbuz CMS.
- If you need to decide which products and fields go to the site — What goes to your website through Elbuz Tunnel.
