DNS Setup

PixelShield routes traffic through our edge network using CNAME records. All game types — Java, Bedrock, and Geyser — use CNAME. The dashboard gives you the exact target after you create a domain.

How it works

When a player connects to play.example.com, DNS resolves your CNAME to our edge network. The edge node receives the connection, runs it through protocol-aware filtering, and forwards legitimate traffic to your backend.

Java Edition domains get a target like a1b2c3d4.proxy.pixelshield.net. Traffic is routed by hostname — multiple Java domains can share the same edge node because the proxy reads the hostname from the Minecraft handshake packet.

Bedrock and Geyser domains get a target like a1b2c3d4.edge.pixelshield.net. These are assigned to specific edge nodes with dedicated UDP ports for RakNet traffic.

Adding the CNAME record

Provider-specific instructions

Cloudflare

1. Go to your domain's DNS tab
2. Click Add record
3. Set Type to CNAME
4. Set Name to your subdomain (e.g., play)
5. Set Target to the value from your PixelShield dashboard
6. Set the proxy status to DNS only (gray cloud icon)

This part is important. Cloudflare's orange-cloud proxy is designed for HTTP traffic. Game protocols (TCP/UDP) won't work through it. Always use gray cloud (DNS only) for game server records.

Namecheap

1. Go to Domain List and click Manage next to your domain
2. Open the Advanced DNS tab
3. Click Add New Record
4. Select CNAME Record
5. Set Host to your subdomain (e.g., play)
6. Set Value to the target from your PixelShield dashboard
7. Save

GoDaddy

1. Go to My Products and click DNS next to your domain
2. Click Add under the Records section
3. Select CNAME as the type
4. Enter your subdomain as the Name
5. Enter the PixelShield target as the Value
6. Save

Other providers

The process is the same everywhere: create a CNAME record pointing your game subdomain to the target shown in your dashboard. If your provider's UI looks different, look for "DNS records" or "DNS management" in their settings.

Verifying your setup

After adding the record:

1. Open your domain in the PixelShield dashboard
2. Click Verify DNS
3. If verification succeeds, you're good — players can connect through our network

If verification fails, give it a few minutes. DNS propagation depends on your provider and TTL settings. You can check propagation manually:

# Check if the CNAME resolves correctly
dig play.example.com CNAME +short

# On Windows (PowerShell)
nslookup -type=cname play.example.com

The output should show your PixelShield target (e.g., a1b2c3d4.proxy.pixelshield.net).

Troubleshooting

DNS not propagating after several minutes?

• Make sure there's no conflicting A record for the same hostname. A records take priority over CNAMEs in most providers — delete the A record first.
• Lower the TTL on any existing record before changing it, so the old value expires faster.
• Some providers cache aggressively. Try flushing your local DNS: ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (macOS).

Cloudflare — players can't connect?

• Check that the proxy status is DNS only (gray cloud). Orange cloud = broken game traffic.
• If you recently switched from orange to gray, wait for the TTL to expire.

Using an SRV record for Minecraft?

• SRV records work fine with PixelShield. Point the SRV target at your CNAME-aliased hostname (e.g., play.example.com), not directly at your origin server. The SRV record handles port mapping; the CNAME handles routing through our network.

Bedrock/Geyser — migrating from an older setup?

• If you previously used an A record for Bedrock or Geyser, the dashboard will show a migration banner. Update your DNS to the new CNAME target and click Confirm Migration once the record is live.