Internal · For the domain owner · Forpsi → Cloudflare

Domain setup.
Four Forpsi domains → four Cloudflare sites.

All four projects are already built and deployed to Cloudflare. They are reachable today at their *.pages.dev / *.workers.dev URLs. The four domains are registered at Forpsi. This guide tells you exactly what to change inside Forpsi's admin to point each domain at its Cloudflare-hosted site.

The short version. Forpsi stays as your registrar (where you renew the domain). DNS — the routing layer — moves to Cloudflare. In Forpsi's admin you change the nameservers from Forpsi's to Cloudflare's. That's the one Forpsi-side change. Everything else happens in the Cloudflare dashboard.

00What the owner literally does

The full version is below. The owner's hands-on work, in one paragraph:

For each of the four domains: add it to Cloudflare to get a pair of nameserver values. Then in Forpsi's admin (admin.forpsi.com) → Domény → click the domain → Nameservery → switch to External nameservers and paste the two Cloudflare values. Save. Wait an hour. In Cloudflare's Pages or Worker dashboard, click Add custom domain. Done.

Time: ~10 minutes hands-on per domain. Cloudflare and Forpsi are both free for this. Forpsi remains the registrar (renewals, ownership); Cloudflare runs the DNS.

01What you have, at a glance

DomainProjectTypeTarget
ln.cash ln-cash Pages ln-cash.pages.dev
hotelia.cz hotelia Worker hotelia.petr-kindlmann.workers.dev
ckrumlov.eu ckrumlov-eu Pages ckrumlov-eu.pages.dev
krumlov.org krumlov-en Pages krumlov-en.pages.dev

Three are static sites on Cloudflare Pages. One (hotelia.cz) is a Next.js app running on a Cloudflare Worker. The DNS shape is similar; the dashboard path differs slightly.

02The decision: change nameservers, or use Forpsi DNS Manager

Two paths. Pick one before starting.

Path A — Switch nameservers in Forpsi to Cloudflare (recommended for all four). In Forpsi's admin, you change each domain's NS records from Forpsi's nameservers to Cloudflare's. Forpsi remains the registrar; Cloudflare runs the DNS. After that, the per-domain setup is a single click in the Cloudflare dashboard for each project.

Cost: free. Time: ~10 minutes per domain, plus up to 24h propagation.

Path B — Keep Forpsi's DNS Manager. You'd stay on Forpsi's nameservers and add CNAME + TXT records inside Forpsi's DNS Manažer. Two problems with this for these specific projects:

  1. Forpsi DNS does not support a real CNAME at the apex (no ALIAS / ANAME). You can point www.ln.cash at ln-cash.pages.dev but not ln.cash directly. The apex would need redirect tricks.
  2. Cloudflare Workers (hotelia.cz) requires the domain to be on a Cloudflare zone. Path B simply does not work for hotelia.cz — you cannot attach a custom domain to a Worker if its DNS is at Forpsi.

Conclusion: Path A for all four. Path B mentioned below in §08 for completeness only.

03Path A · Move DNS from Forpsi to Cloudflare

One-time setup, repeated per domain. Do this once for each of the four before the per-domain sections.

Step 1 — Add the domain in Cloudflare (to get the nameserver values)

  1. Log into dash.cloudflare.com.
  2. Click + Add a domain. Enter the domain (e.g., ln.cash). Pick the Free plan.
  3. Cloudflare scans Forpsi's existing DNS and shows what it found. Review — uncheck any old records you don't want (often the case with parked-domain placeholders). Click Continue.
  4. Cloudflare assigns you two nameservers, e.g.,
    noah.ns.cloudflare.com
    uma.ns.cloudflare.com
    (your exact pair will be different — Cloudflare picks two from a pool). Copy these values somewhere safe.

Step 2 — Switch nameservers inside Forpsi admin

  1. Log into Forpsi at admin.forpsi.com.
  2. Navigate to Domény (Domains) in the left menu. You'll see your list of registered domains.
  3. Click the domain you're moving (e.g., ln.cash).
  4. Find the Nameservery / DNS section. There's usually a button or link labelled something like Změnit nameservery (Change nameservers) or Nastavení DNS (DNS settings).
  5. Switch from Forpsi nameservery (typically ns.forpsi.cz, ns.forpsi.net, ns.forpsi.it) to Cloudflare's two nameservers from Step 1. Some Forpsi screens label this option Externí nameservery (External nameservers).
  6. Save. Forpsi typically registers the change within a few minutes; full global DNS propagation can take up to 24 hours but usually completes in under 1 hour.

What stays at Forpsi: the registration itself. Domain renewals, WHOIS contact info, and ownership are still managed in Forpsi's admin. You're only changing where DNS queries are answered.

Step 3 — Confirm the switch in Cloudflare

  1. Back in Cloudflare dashboard, on the domain's overview page, click Check nameservers now.
  2. Status changes to Active once Cloudflare detects the new nameservers (anywhere from a few minutes to a few hours).
  3. Cloudflare will email you when the activation is complete.

Repeat for all four domains: ln.cash, hotelia.cz, ckrumlov.eu, krumlov.org. You'll get a different nameserver pair for each — make sure to paste the right pair into the right Forpsi domain.

One thing to watch in Forpsi. If any of these domains currently has Forpsi-hosted email (webmail through Forpsi), the email MX records need to be re-added in Cloudflare's DNS before activation, otherwise mail stops working. Cloudflare's initial scan should catch existing MX records — verify in Cloudflare's DNS tab that any MX records pointing to mx.forpsi.com (or similar) are present. If they're not, copy them from Forpsi's DNS Manažer to Cloudflare before the switch.

04ln.cash — point to Pages

ln.cash

Pages

Target: ln-cash.pages.dev

Cloudflare dashboard flow

  1. In the Cloudflare dashboard, go to Workers & Pages → ln-cash.
  2. Open the Custom domains tab. Click Set up a custom domain.
  3. Enter ln.cash. Cloudflare creates the necessary records automatically (CNAME flattening at the apex). Click Activate domain.
  4. Repeat with www.ln.cash if you want a www variant. Cloudflare creates a CNAME from www → ln-cash.pages.dev.

Records that get created (for your reference)

TypeNameValueProxy
CNAMEln.cashln-cash.pages.devProxied
CNAMEwwwln-cash.pages.devProxied

Verify live: https://ln.cash should return the LN Cash homepage within a few minutes.

05hotelia.cz — point to the Worker

hotelia.cz

Worker

Target: hotelia.petr-kindlmann.workers.dev

Hotelia is a Next.js app running on a Cloudflare Worker (via open-next). The custom-domain path is via the Worker's Domains & Routes settings, not the Pages flow.

Cloudflare dashboard flow

  1. Go to Workers & Pages → hotelia.
  2. Open the Settings tab → Domains & Routes.
  3. Click Add → Custom domain. Enter hotelia.cz. Click Add domain.
  4. Cloudflare creates the necessary records and routes traffic to the Worker. SSL certificate provisioning takes 1–5 minutes.
  5. Repeat for www.hotelia.cz if you want the www variant.

Records that get created

TypeNameValueProxy
AAAA / Ahotelia.cz(Cloudflare-managed)Proxied
CNAMEwwwhotelia.czProxied

Why not Pages for hotelia? Because hotelia is a Next.js app with server-side routes (API endpoints, cron jobs). Workers are the right home for that. The Cloudflare dashboard handles the routing for you once you add the custom domain.

06ckrumlov.eu — point to Pages

ckrumlov.eu

Pages

Target: ckrumlov-eu.pages.dev

Cloudflare dashboard flow

  1. Workers & Pages → ckrumlov-eu.
  2. Custom domains → Set up a custom domain.
  3. Enter ckrumlov.eu. Click Activate domain.
  4. Repeat with www.ckrumlov.eu.

Records that get created

TypeNameValueProxy
CNAMEckrumlov.euckrumlov-eu.pages.devProxied
CNAMEwwwckrumlov-eu.pages.devProxied

07krumlov.org — point to Pages

krumlov.org

Pages

Target: krumlov-en.pages.dev

Cloudflare dashboard flow

  1. Workers & Pages → krumlov-en.
  2. Custom domains → Set up a custom domain.
  3. Enter krumlov.org. Click Activate domain.
  4. Repeat with www.krumlov.org.

Records that get created

TypeNameValueProxy
CNAMEkrumlov.orgkrumlov-en.pages.devProxied
CNAMEwwwkrumlov-en.pages.devProxied

08Path B · Keep Forpsi DNS Manager (not recommended)

If you cannot or don't want to change nameservers, you'd add CNAME and TXT records inside Forpsi's DNS Manažer. For these specific four domains it's not a clean fit — see the two blockers below — but the mechanics, if you went that way:

The two blockers

Blocker 1 — Forpsi DNS does not support apex CNAME. Forpsi's DNS Manažer does not offer ALIAS, ANAME, or CNAME-flattening at the zone apex. You can put a CNAME on www.ln.cash → ln-cash.pages.dev, but you cannot put a CNAME on ln.cash itself. The apex would resolve to nothing.

Workarounds: (a) accept that only the www hostname works and configure Forpsi's URL forwarding from ln.cash → https://www.ln.cash; (b) use a third-party redirect service. Both are clunky compared to just moving nameservers.

Blocker 2 — Cloudflare Workers requires a Cloudflare zone. Attaching hotelia.cz to the hotelia Worker requires the domain to be on Cloudflare DNS. There is no path to keep hotelia.cz on Forpsi DNS and attach it to a Worker. If you must keep Forpsi DNS for hotelia.cz, you'd either keep the public URL as hotelia.petr-kindlmann.workers.dev (ugly) or move hotelia off Cloudflare Workers (significant rewrite).

Mechanics, if you proceeded anyway (Pages domains only)

For ln.cash, ckrumlov.eu, krumlov.org — at www hostname only:

  1. In Cloudflare dashboard → the relevant Pages project → Custom domains → Set up a custom domain. Enter www.ln.cash (etc.).
  2. Cloudflare displays the records it needs. Typically a CNAME and a TXT verification record.
  3. In Forpsi admin → Domény → click the domain → DNS Manažer. Add:
    TypeNameValueTTL
    CNAMEwww[project].pages.dev3600
    TXT_cf-custom-hostname(token from Cloudflare)3600
  4. Set up Forpsi URL Forwarding from apex (ln.cash) → https://www.ln.cash. (Forpsi admin → domain → URL Forwarding / Web Forwarding.)
  5. Back in Cloudflare, click Verify. Once verified, SSL provisions in 5–60 minutes.

This is workable but adds a redirect hop, breaks the "ln.cash works" expectation, and complicates analytics. The Path A nameserver change is genuinely easier in every way for these four domains.

09Verifying everything worked

For each domain, after DNS propagates:

  1. Open https://[domain] in a fresh browser tab. The right site should load.
  2. Check the SSL certificate. Click the padlock; the certificate should be issued by Google Trust Services or Cloudflare and cover [domain].
  3. Try https://www.[domain]. It should either render the same site or redirect to the apex.
  4. Use dnschecker.org to confirm propagation across regions if you want a paranoid double-check.

10If something goes wrong

11Suggested order

  1. ln.cash first. Lowest risk — pure static site, no live business depending on it yet. Use it to learn the flow.
  2. krumlov.org next. Same pattern.
  3. ckrumlov.eu next. Same pattern.
  4. hotelia.cz last. Worker-based, so the dashboard path is slightly different. Make sure to test all the API routes and cron jobs after the cutover.

Each domain takes 5–15 minutes hands-on, plus DNS propagation time (usually under an hour, occasionally up to 24h).

Internal — domain setup guide  ·  2026