Wildcard domains

A wildcard domain is a single panel entry that covers every subdomain of a root, so you don’t have to add play.example.com, eu.example.com, na.example.com, … one by one.

How it works

Register a single CNAME at your DNS provider:

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

In the panel, add *.example.com as a single domain entry. The wildcard counts as one entry toward your plan’s domain quota — regardless of how many subdomains are matched at runtime.

When wildcards are the right tool

• You want a flexible naming scheme — players use eu1, eu2, na1, mobile etc. and you don’t want to maintain the list.
• You want to allow staff to create new subdomains without panel access.
• You serve community subdomains and don’t know the names ahead of time.

When wildcards are the wrong tool

• You have a small, stable set of subdomains. Adding 2–3 specific entries is more auditable.
• You want different settings per subdomain — wildcards inherit the network’s settings, so finer-grained control means separate networks.

SRV records and wildcards

Wildcard SRV is not supported:

; This does NOT work:
_minecraft._tcp.*.example.com.   IN   SRV   ...

Each subdomain that needs an SRV record requires its own explicit entry. See SRV records.

Bedrock subdomains and wildcards

The wildcard’s CNAME points at a Java edge (front-*). Bedrock subdomains need a dedicated-IP CNAME (<uid>.ip.infinity-filter.com) and can’t share the same wildcard.

For Bedrock-specific subdomains (bedrock.example.com, mobile.example.com), register a separate CNAME pointing at the dedicated IP.

What’s next