How to Use a Custom Domain for Your Server (SRV Records)

You can't change your server's raw IP. It's fixed to the node, but you don't have to make players type numbers either. ThundraNode can set you up with a free subdomain (e.g. yourname.thundra.xyz), or you can point your own registered domain at your server using a DNS SRV record. Both work; the free subdomain is faster to get running.

Symptoms

• You want players to join with a name instead of an IP:port.
• You bought a domain and aren't sure how to connect it to your server.
• Your address stopped resolving after a change and you're unsure if DNS is still propagating.

Why this happens

Minecraft (and most game servers) connect via an IP and port, shown as your Hostname on the Dashboard's Server Info panel. That underlying address can't be reassigned. It belongs to the node your server lives on. A custom domain or subdomain is just a DNS record that redirects a friendly name to that same IP and port behind the scenes. Java clients can read an SRV record to also carry the port, so players don't need to type :port at all; Bedrock and some other setups still need the port appended manually.

Changing your domain does not hide your original IP from anyone who already has it. If you're dealing with a leaked address or a raider, ask support to change your port or assign a dedicated IP alongside the domain change.

How to fix it

1. Open the Dashboard and note your current Hostname (shown as IP:PORT) under Server Info: you'll need this to point any domain correctly.
2. Choose your path:

• Free ThundraNode subdomain: open a support ticket and request a subdomain name (e.g. yourservername.thundra.xyz). Staff configure it on their end. Note the address may still include a port, similar to yourname.thundra.xyz:PORT.
• Your own domain: register it with a third-party provider (e.g. GoDaddy), then create a DNS SRV record of type _minecraft._tcp pointing to your server's hostname, with the port field set to your server's port. This lets Java players connect without typing the port.

1. Save the DNS changes and wait for propagation: typically 1-3 hours, occasionally up to 24 hours.
2. Test the new address once it's live. See How to Connect to Your Minecraft Server for connection steps, or ping the domain from a terminal to confirm it resolves.
3. If you're moving away from a leaked or abused IP, also ask support about changing your port or ordering a dedicated IP: check How to Find or Change Your Server IP and Port for what's possible.
4. If the panel's subdomain creation tool throws an error, don't keep retrying: this has been a known intermittent bug. Open a ticket and staff can set it up manually.

Still stuck?

If propagation has passed 24 hours with no change, your SRV record looks wrong, or the panel's subdomain tool keeps erroring out, open a support ticket with your domain name and current hostname. Staff can verify the DNS setup or configure it manually on their side while the tool is fixed.