Bring your own domain. You did buy one, right?
Your site already has an address like yourname.flff.site. To use your own, say example.com, point it at flff in one of two ways.
Both start in your site panel: open your sites, choose Domain, and enter the domain. The panel shows the exact records for your site, with copy buttons, and checks them live. This page explains what they mean. (Free one-hour sites can't have their own domain.)
Which way?
| Way 1: flff's nameservers | Way 2: keep your DNS, add a CNAME | |
|---|---|---|
| Best for | A domain used only for this site, or one you'd like us to look after | A domain that also runs email or other services you'd rather not touch |
Works for the bare domain (example.com) | Yes | Only with an ALIAS record or an A record (see below) |
| Who runs the domain's DNS | flff (our servers, ns1.flff.fi and ns2.flff.fi) | Whoever runs it now |
| Certificate (https) | Automatic | Automatic |
| What you change | Two nameservers at your registrar, after copying your existing records to us | One to three records at your DNS host |
Step 0: prove it's yours
Both ways start with one TXT record, so nobody can attach a domain they don't own. The panel gives you yours; it looks like this:
| Type | Name | Value |
|---|---|---|
| TXT | _flff.example.com | flff-verify=3f9c… (your code, from the panel) |
Some DNS hosts want only the first part of the name (_flff) and add your domain themselves. If yours does, enter just _flff.
Way 1: use flff's nameservers
Your registrar (where you bought the domain) says which servers answer for it. Point that at us and we run the domain's DNS: the site, www, the certificate, and anything else you ask for.
- Write down your current records first. Especially MX (email), TXT (email security such as SPF and DKIM, and services' verification records), and any subdomains you use. Send them to hello@flff.fi and we copy them into your zone before you switch. Skip this and your email stops.
- Turn off DNSSEC at your registrar if it's on. Otherwise the domain stops resolving after the switch. (We don't sign customer zones yet.)
- Replace the nameservers with these two, and remove any others:
ns1.flff.fiWhere to find it (menu names change now and then):
ns2.flff.fi- GoDaddy: the domain's settings → Nameservers → Change → use your own nameservers.
- Namecheap: Domain List → Manage → Nameservers → Custom DNS.
- Squarespace Domains (including former Google Domains): the domain → DNS → Nameservers → use custom nameservers.
- Porkbun: the domain's details → Authoritative nameservers.
- Cloudflare Registrar doesn't allow other nameservers. Use Way 2.
- Wait. Usually minutes, sometimes up to 48 hours. The panel shows ✓ next to "Nameservers" once the world agrees.
Way 2: keep your DNS and add a CNAME
Leave the nameservers alone and add records where your DNS lives now. Don't change your MX records; email carries on as it is.
For www or another subdomain
| Type | Name | Value |
|---|---|---|
| CNAME | www.example.com | yourname.flff.site |
Remove any other A, AAAA or CNAME record with the same name first; a name can't have both.
For the bare domain (example.com)
DNS doesn't allow a CNAME on the bare domain, so pick the first of these your DNS host offers:
- An ALIAS, ANAME, or "CNAME flattening" record pointing at
yourname.flff.site. Cloudflare, DNSimple, Namecheap and many others offer one. - Forwarding: have the registrar redirect
example.comtohttps://www.example.com, and use the CNAME above forwww. - An A record to
67.225.165.199. It works, but if our address ever changes you'll need to update it. We'll email you if it does.
After that
- When the TXT record and either the nameservers or the CNAME check out, the panel says Verified.
- We switch the domain on for your site. That's done by hand for now, usually within a day.
- The certificate is issued automatically, and the panel says Active. Your flff.site address keeps working too.
- Then tell your AI: "My site is at example.com now." It'll use it in links.
Malfunctions
| You see | What it means |
|---|---|
| "The domain wasn't found in DNS" | It isn't registered, it's spelt differently, or it expired. Check at your registrar. |
| Nameservers still show the old ones | The change hasn't spread yet (give it up to 48 hours), or it didn't save at the registrar. |
| "Points to" shows another address | An old A or CNAME record is still there. Remove it, keeping only the one from the panel. |
| Your DNS host refuses a CNAME on the bare domain | Expected: use ALIAS, forwarding or the A record, as above. |
| "Already connected to a site" | Someone (maybe you) added it to another site. Remove it there first, or write to us. |
| Email stopped after switching nameservers | Your MX records weren't copied over. Send them to us now, or switch the nameservers back while we sort it out. |
Still stuck? Write to hello@flff.fi with the domain and what the panel shows.