Custom Domain Setup

1. The free URL — no setup needed

Every Fluxeta site gets two public URLs the moment you sign up:

• Path URL — https://fluxeta.com/@your-handle  ← always works
• Subdomain URL — https://your-handle.fluxeta.com  ← cleaner, same site

Both open the same site; use whichever you prefer when sharing. You do not need to touch DNS, buy a domain, or configure anything to use either. If a URL is not opening on your phone or computer, skip to Section 8 — Troubleshooting. The Custom Domain tab in Settings only applies when you want to use your own domain (e.g. blog.yourname.com) instead.

2. Custom domain — overview

A custom domain lets your site live at an address you own — yourname.com, blog.yourname.com, newsletter.yourbrand.in — instead of the default yourname.fluxeta.com. It is better for brand, SEO continuity if you are migrating from WordPress / Substack / Ghost, and email deliverability if you later send newsletters from the same domain.

The process is three steps:

1. Tell Fluxeta the domain you want to use (Dashboard → Settings → Custom Domain).
2. Add two DNS records at your registrar (one CNAME to point traffic at us, one TXT so we can prove you own it).
3. Click Verify DNS in Fluxeta. We auto-issue a free SSL certificate within minutes.

You do not need to transfer the domain to us. It stays at your current registrar (GoDaddy, Namecheap, Cloudflare, Hostinger, BigRock — any of them).

3. Subdomain vs root domain

Decide what your public URL should be before you add DNS records.

Subdomain — recommended

Examples: blog.yourname.com, newsletter.yourbrand.in, learn.yourname.com.

• Simple, fast, no conflicts with your main website.
• Uses one CNAME record — the universally supported DNS type.
• Your main site (yourname.com) keeps running wherever it already runs.

Root domain (apex) — advanced

Example: yourname.com itself.

• Only choose this if Fluxeta will be the only thing at yourname.com. Anything else that was there (an old WordPress install, a landing page) will stop resolving.
• Classic DNS does not allow CNAME at a root, so you'll either need an A record (we give you an IP in Settings) or a provider that supports CNAME flattening / ALIAS / ANAME (Cloudflare does, so does Hostinger's newer DNS panel).

When in doubt, start with a subdomain. You can move to the root later.

4. Add your domain in Fluxeta

1. Open Dashboard → Settings → Custom Domain.
2. Type the full domain (no https://, no trailing slash). Examples:
   • blog.yourname.com (subdomain — recommended)
   • yourname.com (root)
3. Click Save Domain.
4. Fluxeta reveals the DNS records you need to add and a TXT verification token unique to your site.

Saving the domain does not switch your site over yet. The old free subdomain keeps working while DNS propagates.

5. Add the DNS records at your registrar

After saving the domain, Fluxeta shows two records. Add them exactly as shown in your Fluxeta Settings — the examples below use placeholders.

For a subdomain (e.g. blog.yourname.com)

Name field tip: some registrars want just the sub-part (blog), others want the full host (blog.yourname.com). Both are correct — the registrar fills in the rest. If unsure, type only the sub-part first.

For a root domain (e.g. yourname.com)

If your registrar is Cloudflare, you can keep the CNAME form and enable CNAME flattening at the root — set @ CNAME fluxeta.com and Cloudflare does the right thing.

Remove conflicting records

If an older A, AAAA or CNAME record already exists for the same name (e.g. an old blog record pointing to Blogger, WordPress or an email forwarder), you must delete it before adding the new one. Two conflicting records for the same host cause intermittent failures.

6. Registrar-specific guides

DNS panels differ a little across providers. The CNAME + TXT values are always the same — only the UI changes.

• GoDaddy: My Products → DNS → Add → choose CNAME, Name = blog, Value = fluxeta.com, TTL = 1 Hour. Repeat for TXT.
• Namecheap: Domain List → Manage → Advanced DNS → Add New Record → CNAME Record, Host = blog, Value = fluxeta.com, TTL = Automatic.
• Cloudflare: DNS → Records → Add record → Type = CNAME, Name = blog, Target = fluxeta.com. Important: set the proxy toggle to DNS only (grey cloud) at first — once your site is live and SSL is issued, you may turn the orange cloud on.
• Hostinger: hPanel → Domains → Manage → DNS / Nameservers → Add new record → CNAME, Name = blog, Target = fluxeta.com.
• BigRock / HostGator India: cPanel → Zone Editor → Add Record → CNAME, Name = blog.yourname.com. (with trailing dot), CNAME = fluxeta.com..
• Google Domains / Squarespace Domains: DNS → Custom records → Add → Host = blog, Type = CNAME, Data = fluxeta.com.
• AWS Route 53: Hosted zone → Create record → Record type = CNAME, Record name = blog, Value = fluxeta.com, TTL = 300.

7. Verify & wait for SSL

1. DNS changes typically propagate in 5–30 minutes, but your registrar may need up to 24 hours. Grab a coffee — this part is out of our hands.
2. Check propagation at dnschecker.org. Enter your domain, select CNAME. When most locations show green ticks pointing to fluxeta.com, you are ready.
3. Back in Dashboard → Settings → Custom Domain, click Verify DNS.
4. On success, we issue a free Let's Encrypt SSL certificate within 1–3 minutes. Your site is now live on HTTPS at your custom domain.

Your original free subdomain (your-handle.fluxeta.com) keeps working forever as a backup — Fluxeta auto-redirects it to your custom domain so existing links don't break.

8. Troubleshooting

"DNS error" / "This site can't be reached" on my free fluxeta.com subdomain

Try these in order — fixes 95% of cases:

1. Open the link on a different network (switch from mobile data to Wi-Fi or vice versa). If one works, the issue is DNS caching on the other network.
2. On Android: Settings → Network & Internet → Private DNS → set to Automatic. A custom Private DNS provider (NextDNS, AdGuard, Cloudflare 1.1.1.1 for Families) can block newly-created subdomains for a few hours.
3. Try an incognito / private window, or a different browser.
4. Restart the device. Phones aggressively cache DNS failures for up to 24 hours.
5. Check dnschecker.org — enter your subdomain (e.g. yourname.fluxeta.com) with type A. If you see green ticks worldwide, DNS is healthy and the problem is purely local to your network.

If none of the above works, email us (details below) with the exact URL and a screenshot of the dnschecker.org result.

Custom domain says "Verification pending" after 1 hour

• Check the TXT record exists: visit https://dnschecker.org/#TXT/dxp-verify.yourname.com. The token value must match the one shown in Settings exactly.
• Confirm you used the correct name — if your root domain is yourname.com and you want blog.yourname.com, the TXT name is dxp-verify.blog, not dxp-verify.
• Some registrars (GoDaddy, old BigRock) take 1–4 hours even after they say "saved". Give it time.

Site loads but shows "Not secure" / certificate warning

• SSL issuance takes 1–3 minutes after Verify DNS succeeds. Reload after a few minutes.
• On Cloudflare, make sure SSL/TLS mode is set to Full (not Flexible). Flexible mode causes redirect loops.
• If using Cloudflare with the orange cloud (proxied) and you added the domain to Fluxeta before enabling proxy, pause the proxy (grey cloud), click Verify DNS again, wait for SSL, then re-enable the orange cloud if desired.

"Too many redirects" after switching

Almost always Cloudflare set to Flexible SSL. Change it to Full (strict).

Email on my domain stopped working after adding the custom domain

This only happens if you pointed the root domain at Fluxeta and had email on the same domain. Fluxeta only touches web traffic — your MX records for email are separate and should not be changed. If email broke, check that your old MX records are still intact in your DNS panel.

9. Still stuck?

Email [email protected] with:

• The exact URL that is failing.
• A screenshot of your DNS records at your registrar.
• A screenshot of dnschecker.org for the same domain (CNAME or A, whichever you set).
• Whether the issue is only on one device/network or everywhere.

We usually reply within one working day (Mon–Sat, 10:00–19:00 IST).