Connecting your own domain
About 10 minutes, plus waiting for DNS
A page you publish on SiteFrenz can sit on a domain of your own — for example warungpakbudi.com — not only on our subdomain. This guide is for anyone who has never touched a DNS setting.
Before you start, have two things ready: a domain you have already bought, and access to wherever you bought it (Niagahoster, Rumahweb, Domainesia, GoDaddy, Cloudflare — any of them). You do not need hosting. The domain alone is enough.
What you actually do
Two things, and you need both:
- Proving the domain is yours — by adding one line of text (a TXT record) that only whoever controls the domain can add.
- Pointing visitors at our server — with one A record aimed at our IP address.
Without the first, we will not issue you a security certificate. Without the second, nothing reaches your page.
The steps
- Add your domain in the extension
Open the Sites tab, pick the page that should sit on that domain, then enter the domain name with no
https://and with nowww. Justwarungpakbudi.com. - Copy the two records it shows
The extension shows exactly what to add. It looks like this:
The TXT value is unique to your domain — do not use someone else's, it will not match.Type Name Value TXT _sitefrenzsitefrenz-verify=…the value differs per domain — copy it from the extensionCNAME wwwconnect.sitefrenz.web.idSome providers do not allow a CNAME on the root domain (with no
www). If yours is one of them, the extension also shows an A record instead — use that one. - Open your domain's DNS settings Look for a menu called DNS Management, Manage DNS, Zone Editor, or Nameservers. It sits in a different place at every provider; the next section shows where it is at the most common ones.
- Add both records
If the Name or Host field asks for something, write
_sitefrenzfor the TXT one and@for the A one. The sign@means "the domain itself". If there is a TTL field, leave it as it is. - Wait a moment, then press Verify DNS takes time to propagate — usually 5 to 30 minutes, sometimes a few hours. If verification fails, wait ten minutes and try again. That is normal, not a sign something is wrong.
- Done — we handle the certificate Once verified, an HTTPS certificate is issued automatically within minutes and renews itself forever. You never have to touch it again.
CNAME or A record? Use a CNAME where you can. If we ever move servers, a CNAME follows by itself — an A record you have to change by hand, and until you do, your client's site is down.
Where to find the DNS settings
| Service | The route |
|---|---|
| Niagahoster | Member Area → Domain → pick your domain → Manage DNS |
| Rumahweb | Clientzone → Domain → Manage DNS |
| Domainesia | Client Area → Domain → DNS Management |
| Dewabiz | Member Area → Domain → Manage DNS |
| Cloudflare | Pick the domain → DNS → Add record. For the A record, set Proxy status to DNS only (grey cloud), not Proxied. |
| GoDaddy | My Products → Domain → Manage DNS |
| Hostinger | hPanel → Domains → DNS / Nameservers |
A note for Cloudflare users. If you set the A record to Proxied (orange cloud), Cloudflare holds the traffic and our certificate cannot be issued. Set it to DNS only until the domain is live. After that you can turn the proxy on if you want.
If it does not work
| Symptom | Usually because |
|---|---|
| Verification keeps failing | DNS has not propagated yet. Wait ten minutes and try again. If an hour has passed, check the record name is right _sitefrenz and the value is copied whole, with no space at either end. |
| Verified, but the page still will not open | The certificate is being issued. Give it five minutes. |
| The browser says it is not secure | The record does not point at us yet, or Cloudflare is still proxying it. |
| It says active, but it will not open on your computer | Your own DNS cache. If you opened the domain before the records were added, the “does not exist” answer got cached too — and .my.id it keeps that for up to 48 hours. The page is already live for everyone else. Check from a phone on mobile data, or switch your device's DNS to 1.1.1.1. |
| An old page keeps opening | Your browser cache or your old DNS. Try it in a private window. |
| The domain was refused | That domain is already on another account, or it is written wrongly. Write it with no https://, with no www, and with no trailing slash. |
What you need to know
- Pages on your own domain can be indexed by Google, unlike pages on our subdomain. That is exactly what a domain of your own is for.
- What is on the page is entirely your responsibility. Read section 7 of the Terms and Conditions before putting up a page for a client.
- No uptime guarantee. If the site genuinely matters to your client's business, use hosting that sells an uptime guarantee — we do not sell one.
- One domain per page. If you have several clients, each one uses their own domain.
Still stuck? Message +62 899 4980 352 with your domain name, and say which step you reached.