Docs
Setup instructions for connecting your Minecraft servers to Covariant Game.
DNS setup
Your DNS records tell players where to connect. To protect your server, point them at us instead of your backend. You can use either a CNAME or an SRV record. The examples below use Cloudflare, but any DNS provider works the same way.
1. Log in to your DNS console
Sign in to your DNS provider and select the domain you want to protect.
2. Remove existing DNS records
Delete any records that point to your backend server’s IP. If players (or attackers) can still resolve that IP, they can bypass protection and reach your server directly.
Important: if your backend IP was ever public, ask your provider for a new one. An attacker who already knows the old IP can keep bypassing protection.
3. Create a protected DNS record
CNAME setup
- Record type: CNAME
- Name: the subdomain players use, such as
playforplay.example.com. For the root domain, leave the name blank or use@. - Target: the protected CNAME shown in your dashboard.
- TTL: 1 to 2 minutes (set to auto on Cloudflare).
- Proxy: turn the Cloudflare proxy off (grey cloud, not orange).
On Cloudflare, CNAME records are flattened automatically, so the root domain works the same way as any subdomain. Most modern DNS providers support this too — if yours does, you can use a CNAME for the root domain.
Your dashboard shows the exact verification record for every domain you add. Base domains (like example.com or example.co.uk) are verified with a TXT record — the same as wildcards — because a CNAME cannot sit on the name that also serves the site.
SRV setup (only if your provider cannot flatten the root domain)
If your DNS provider does not support CNAME flattening, you cannot put a CNAME on the root domain. In that case, use an SRV record instead so players can connect with just example.com (Java servers only). The SRV record tells Minecraft clients which hostname and port to use:
- Record type: SRV
- Name:
_minecraft._tcp(your provider may split this into service_minecraftand protocoltcp) - Priority:
10 - Weight:
0 - Port:
25565 - Target: the protected CNAME shown in your dashboard (the same hostname a CNAME would point to)
The SRV record must have a target: it tells clients which protected hostname to actually connect to. Without it, the record does nothing.
Wildcard domains
If you registered a wildcard domain (*.example.com) in your dashboard, create a single wildcard CNAME instead of one record per subdomain:
- Record type: CNAME
- Name:
* - Target: the protected CNAME shown in your dashboard
The wildcard CNAME is required: it routes both the ownership-verification lookup and the automatic TLS certificate challenge to us, so every subdomain of your domain gets a working certificate without any per-subdomain setup. Wildcard certificates are issued automatically once the domain is verified (one wildcard certificate at a time per server).
Once you save, the change can take a few minutes to spread across the internet.