1) Buy a domain

Purchase a domain from any registrar (examples: OVH.pl, Domeny.pl, Home.pl, Nazwa.pl). After checkout, open your domain’s DNS panel.

2) Create the A record (points the name to your server IP)

Delete any default A record first if your panel requires it, then add a new one.

3) Create the SRV record (tells Minecraft which port to use)

If your server uses a non-default port (anything other than 25565), add an SRV record so players can join with just the domain.

Some panels present SRV as a single value line. The finished value looks like:

Example from the instructions:

Examples

A record → mc.xyz.pl

SRV record for mc.xyz.pl on port 1234

Checklist & Troubleshooting

• Propagation: DNS changes can take a few minutes to apply. Give it time and try again.
• Trailing dot: For SRV targets, many panels require a trailing dot (e.g., mc.xyz.pl.).
• Correct target: The SRV Target must be a name that ultimately points (via A/AAAA) to your server IP.
• No port in A: If you added a port to the A record by mistake, remove it and set the SRV correctly.
• Default port: Running on 25565? You can skip SRV and just use the A record.

Want a clean, memorable URL like dc.yourdomain.com that redirects straight to your Discord? Here’s a simple, reliable setup using a DNS record and a 301 redirect rule (e.g., on Cloudflare).

What You’ll Set Up

• A subdomain (e.g., dc or discord) in your DNS.
• A permanent redirect (301) that forwards all traffic to your Discord invite link.

Step 1 — Create the DNS Record

In your DNS dashboard, add an A record for the subdomain you want to use.

If your provider supports a dedicated “URL Redirect/Forward” record, you can use that instead of a dummy A record.

Step 2 — Add the Redirect Rule (301)

Create a forwarding rule so every request to your subdomain goes to your Discord invite.

Example pattern and target

Using a wildcard like *dc.yourdomain.com/* ensures any path (e.g., /invite) also redirects cleanly.

Step 3 — Test Your Shortlink

1. Wait a few minutes for DNS and rules to apply.
2. Visit dc.yourdomain.com in a browser. It should land on your Discord invite.
3. Optionally test with curl -I https://dc.yourdomain.com to see the HTTP/1.1 301 and Location header.

Troubleshooting

It doesn’t redirect—just shows a blank page or error.

• Ensure the DNS record for dc exists and (on Cloudflare) is Proxied.
• Confirm the rule’s pattern matches your hostname exactly (e.g., dc.yourdomain.com/*).
• Use https:// in the destination (Discord requires HTTPS).

Redirect loop or no response.

• Make sure your destination is not pointing back to the same subdomain.
• Clear browser cache or test in a private window after changing from 302 → 301.