Custom domains

On Plus (3 domains) and Pro (20 domains) you can point a hostname you own, like play.example.com, at a tunnel.

1. Add the domain

In Domains, enter the hostname and pick a tunnel. Enzonic hostnames (enzonic.dev, enzonic.com, play-mc.cc) are refused.

2. Prove you own it (TXT)

Create the TXT record shown, for example:

_enzonic-relay.play.example.com  TXT  "enzonic-relay-verify=<32 hex characters>"

Then press Verify. The control plane looks the record up over DNS over HTTPS (Cloudflare, then Google) and needs the exact value. DNS changes can take a few minutes to appear.

3. Route players

Pick one of these, depending on the tunnel:

Java with a CNAME

play.example.com  CNAME  yourname.r.enzonic.dev

Players type play.example.com. The handshake carries that host and the relay routes it through the verified-domain table.

Java with SRV

_minecraft._tcp.play.example.com  SRV  0 5 25565 yourname.r.enzonic.dev

Use SRV to keep the apex free or when you cannot use a CNAME. Vanilla clients put the SRV target in the handshake, so the relay routes by your tunnel name; the verified domain is also accepted in case a client sends the original host.

Bedrock

play.example.com  CNAME  <home node>.relay.enzonic.dev

Bedrock has no SRV records and no hostname in its handshake, so players still type the tunnel's dedicated port: play.example.com plus the port shown on the tunnel.

Staying verified

A hostname can be verified by one account only. Verified domains are re-checked every 6 hours; after 3 failed checks in a row the domain stops routing. Deleting a domain removes it from routing at once. Keep the TXT record in place.