Domains

A domain is a hostname players use to connect (play.example.com, eu.example.com, …). Each Java domain on a network is verified individually and pointed at the Infinity-Filter edge via a CNAME.

The Domains page has two tabs: Java domains (this page) and Bedrock domains, for players joining through Geyser (see Bedrock domains).

Where to find it

Open Network → Domains.

The Java domains table lists every Java domain on this network with its last update and creation dates, and edit/delete actions.

Adding a domain

Click Add domain, type the hostname (e.g. play.example.com), and save.

The domain is checked when you add it: it must already point to Infinity-Filter — its CNAME from the CNAME card — or the domain must have the TXT verification record. Otherwise the panel refuses it with Domain not verified: create the record, wait a minute, and add it again.

The CNAME card

On the right side of the Domains page, the CNAME Domain card lets you pick the region for the domain.

Click the flag of the region you want to use. The card shows (click a field to copy its value):

• A CNAME target your domain must resolve to — <uuid>.front-<location>.infinity-filter.com. Pointing at it both routes traffic and verifies ownership, so this is all the domain needs.
• A TXT record — infinity-filter-verification=… — created on the root domain (Name = @) by pasting the text the panel shows. It’s an optional fallback (the CNAME already verifies the domain), but recommended so verification survives if the CNAME is ever unreachable.

The selected region is remembered in the panel (localStorage), so it’s the default the next time you open the page.

Picking the right region

Use the Latency Test before picking a region. The right region is whichever PoP gives the lowest RTT between your backend and your player base. See Choosing a region for the full rule.

DNS at your registrar

Create the records exactly as the panel printed them. See DNS setup for the full reference, but the gist:

; CNAME — player-facing hostname → IF edge. Required; this alone verifies the domain.
play.example.com.   300   IN   CNAME   {uuid}.front-de.infinity-filter.com.

; TXT — recommended fallback on the root domain (Name = @). The CNAME already proves ownership.
example.com.   300   IN   TXT   "infinity-filter-verification=..."

Verification

Verification happens when you add the domain: the CNAME pointing at the Infinity-Filter edge proves you control it, and so does the TXT record of its root domain. Once added, the domain routes player traffic as soon as its CNAME resolves.

With the TXT record in place, any address of that domain can be added right away — even before its CNAME points to Infinity-Filter (handy to move from another protection without downtime). The guided setup checks the records for you every 10 seconds and adds the domains once they’re detected.

If verification fails, see DNS issues troubleshooting.

Editing a region after the fact

Switching CNAME region is non-disruptive:

• Existing player connections keep their backend — they don’t drop.
• New connections start using the new region as DNS propagates.

Before flipping, allowlist the new PoP’s IP ranges at your backend firewall.

Deleting a domain

Click the delete icon on a row. The domain is unregistered immediately on Infinity-Filter — but the DNS at your registrar continues to point at our edge until you remove or repoint the CNAME. While it still points at us, players hitting the hostname see the protected fallback message even though the network no longer claims that domain.

Wildcards

Instead of adding subdomains one by one, register a single wildcard entry:

*.example.com.   300   IN   CNAME   {uuid}.front-de.infinity-filter.com.

The wildcard counts as one entry in the panel and on the plan quota. It does not cover the apex (example.com) — the apex must still be added separately if you want it to resolve through Infinity-Filter.

Wildcard availability depends on the plan. See Wildcard domains.

Bedrock domains

Domains for Bedrock players (bedrock.example.com, mobile.example.com, …) are managed in the Bedrock domains tab — not in the Java domains table. They point to your dedicated IP hostname ({uid}.ip.infinity-filter.com) instead of the CNAME card, and Infinity-Filter creates a certificate for each of them, which phones and tablets need to join.

Adding a Bedrock domain to the Java domains table fails with “Domain not verified”: its verification is Java-only.

See Bedrock domains and Geyser (Bedrock).

Plan limits

Domain quota (apex + each subdomain + each wildcard) depends on your plan. The current limit and usage are shown on the Domains page. To raise the limit, open Billing → Plans from the sidebar.

What’s next