Forpsi DNS setup

If your domain is registered at Forpsi, connecting it to Redirect Supply means changing a few records in Forpsi’s DNS editor. Your domain stays at Forpsi, and your registration and email don’t change. It takes about five minutes, and Forpsi usually publishes changes within half an hour.


Before you start

You need two things ready before you open Forpsi.

Add the domain in Redirect Supply


DNS records shown for a domain in Redirect Supply


Add your domain in Redirect Supply first. Its settings page shows the records you’ll need, including a TXT value that’s unique to your domain. Keep that page open in another tab. This guide covers a root domain like brand.cz. If you’re connecting a subdomain like go.brand.cz, the DNS setup guide explains the differences.

Check that Forpsi DNS is in use

Forpsi only lets you edit records when the domain uses Forpsi’s DNS servers. If the Editace DNS záznamů option doesn’t appear for your domain, it’s using DNS servers somewhere else. Either add the records with that provider, or switch the domain to Forpsi’s DNS servers first. The Cloudflare DNS setup guide covers the most common other case.

Open the DNS editor at Forpsi

All the changes in this guide happen on one screen.

Find Editace DNS záznamů

Sign in through Administrace on the Forpsi website and open Domény from the main menu. Select your domain, then choose Editace DNS záznamů. A form for new records sits at the top, and your current records are listed below it.

Records you’ll see there

If the domain was ever connected to Forpsi hosting, it already has an A record on the root domain and a record for www pointing to Forpsi’s servers. Those use the names Redirect Supply needs. Not sure what else counts? The conflict table on your domain’s page in Redirect Supply lists every record that blocks the setup.

Clear the way

Before adding anything, remove what’s already pointing your domain elsewhere.

Remove old root and www records

Use Smazat at the end of each row to delete A records with an empty hostname and any record on www. If there’s an AAAA record with an empty hostname, delete it too, or visitors on IPv6 will keep reaching the old server. Deleting can’t be undone, so note down the old values first if you might need them.

Remove Forpsi redirects

If the domain is redirected through Forpsi webhosting, remove that redirect first. Forpsi’s own redirect competes with Redirect Supply’s records for the same domain.

Leave email records alone

MX records and email TXT records like SPF or DKIM keep your email working. They don’t affect redirects, so leave them exactly as they are.

Add the Redirect Supply records

You’ll add four records using the form at the top. Forpsi doesn’t accept @: leave the Hostname field empty for the root domain, and enter only the prefix for anything else. Don’t add a dot at the end of values, even if another guide shows one. Keep the default TTL of 1800 seconds.


Name

Type

Value

www

CNAME

proxy.redirect.supply

(leave empty)

A

188.114.96.9

(leave empty)

A

188.114.97.9

_cf-custom-hostname

TXT

Value from your domain’s settings page


Note: Forpsi doesn’t accept @, so leave the hostname empty for the root domain.

Add two A records for the root domain

Choose A as the Typ, leave Hostname empty, and enter 188.114.96.9 as the Hodnota. Save it, then add a second A record with an empty hostname and the value 188.114.97.9.

Add the www CNAME

Choose CNAME, enter www as the hostname and proxy.redirect.supply as the value, and save.

Add the TXT record

Choose TXT, enter _cf-custom-hostname as the hostname, paste the value from your domain’s settings page in Redirect Supply, and save. On some less common domain endings, Redirect Supply also asks for an _acme-challenge TXT record. Add it the same way if you see it. This rarely happens with .cz domains.

Check the list

Each record appears in the list below the form once it’s saved. Make sure all four are there, and that no other A, AAAA or www record is left on the same names.

Check the status in Redirect Supply

Once the records are saved, you’re done in Forpsi.

Check the conflict table


Conflict table in Redirect Supply showing a record to remove


You don’t have to wait to find out if something’s wrong. Your domain’s page in Redirect Supply shows a conflict table with the records currently on your domain. Anything that blocks the setup, like an old Forpsi A record or a leftover www record, is flagged there along with what to do about it. Fix those first, and the rest is just waiting.

How long it takes

Forpsi says changes usually take effect within 30 minutes. If you just moved the domain to Forpsi’s DNS servers, allow up to 24 hours.

When the domain goes Active


Domain showing Active status in Redirect Supply


Redirect Supply checks your records automatically. When it finds them, the domain switches to Active and HTTPS is issued on its own, with no extra steps from you. See Domain statuses for what each status means along the way.

Forpsi-specific issues

Most problems on Forpsi come from the hostname format or a leftover hosting record.

Forpsi won’t accept the root record

You probably typed @ in the Hostname field. Forpsi doesn’t support it. Leave the field empty instead.

Editace DNS záznamů isn’t there

The domain uses DNS servers outside Forpsi. Add the records with the provider your nameservers point to, or switch the domain to Forpsi’s DNS servers first.

The old website still loads

An old A or AAAA record on the root domain, or a Forpsi hosting redirect, is still active. Delete it and check again in a private window after half an hour.

The domain is stuck on Pending

Open the conflict table on your domain’s page in Redirect Supply. It shows which record is blocking the setup, usually a leftover root A record or an old www record. Remove what it flags and wait a few minutes. Record conflicts covers the common cases.

Still weighing Forpsi redirects?

See how Forpsi’s domain redirect compares to Redirect Supply on HTTPS, path rules and independence from hosting.

Still weighing Forpsi redirects?

See how Forpsi’s domain redirect compares to Redirect Supply on HTTPS, path rules and independence from hosting.

Missing something?

If there's a feature you need that Redirect Supply doesn't have yet, we want to hear about it. Every request goes straight to the team building this.

Missing something?

If there's a feature you need that Redirect Supply doesn't have yet, we want to hear about it. Every request goes straight to the team building this.

Registrar guides

/

Forpsi DNS setup